Triple
T29043300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Squirrel |
E738057
|
entity |
| Predicate | associatedWithDesignation |
P70371
|
FINISHED |
| Object | AS350 |
E238444
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: AS350 | Statement: [Squirrel, associatedWithDesignation, AS350]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithDesignation Context triple: [Squirrel, associatedWithDesignation, AS350]
-
A.
associatedDesignation
chosen
Indicates that one entity is linked to or identified by a particular designation, title, or label connected with it.
-
B.
hasDesignationFor
Indicates that one entity assigns or holds a specific title, label, or formal designation for another entity.
-
C.
associatedWithDesign
Indicates that there is a connection or involvement between an entity and a particular design, design process, or design-related activity.
-
D.
associatedWithDesignerLabel
Indicates a relationship where something is linked or connected to a particular designer label, typically signifying brand association or attribution.
-
E.
hasDesignationBy
Indicates that one entity has been formally assigned or labeled with a specific designation by another entity.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a0301289dbc8190a4372958d3451171 |
completed | May 12, 2026, 10:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a251f70f5bc8190aca497dd6c4e62f0 |
completed | June 7, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_6a0300d4185c8190a383d5da3659bc4f |
completed | May 12, 2026, 10:28 a.m. |
Created at: April 28, 2026, 10:03 a.m.