Triple
T35632919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellow Cars |
E1029635
|
entity |
| Predicate | hasNicknamedOperator |
P183813
|
FINISHED |
| Object | LARY |
—
|
NE NERFINISHED |
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: LARY | Statement: [Yellow Cars, hasNicknamedOperator, LARY]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNicknamedOperator Context triple: [Yellow Cars, hasNicknamedOperator, LARY]
-
A.
hasNicknamedFeature
Indicates that an entity possesses a feature or attribute that is commonly referred to by a specific nickname.
-
B.
hasNicknameFunction
Indicates that one entity serves as a nickname or informal alternative name for another entity.
-
C.
hasNicknamedEntityType
Indicates that an entity is associated with another entity type specifically in the role of being its nickname or informal name.
-
D.
hasNicknameForm
Indicates that one entity is a nickname or informal variant form of another entity’s name.
-
E.
hasNicknames
Indicates that an entity is known or referred to by one or more alternative informal names.
- F. None of above. chosen
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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a34e80dc8190980d5b7b0b91341d |
completed | May 3, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:05 p.m.