Triple
T33675712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randall Raines |
E862753
|
entity |
| Predicate | givesNicknameTo |
P44320
|
FINISHED |
| Object | 1967 Ford Mustang Shelby GT500 |
—
|
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: 1967 Ford Mustang Shelby GT500 | Statement: [Randall Raines, givesNicknameTo, 1967 Ford Mustang Shelby GT500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givesNicknameTo Context triple: [Randall Raines, givesNicknameTo, 1967 Ford Mustang Shelby GT500]
-
A.
nickNameGivenBy
chosen
Indicates that one entity assigns or uses a particular nickname for another entity.
-
B.
hasAffectionateNicknameFor
Indicates that one entity uses or assigns a fond, affectionate, or endearing nickname to another entity.
-
C.
dedicatedToOrNicknameOf
Indicates that one entity is either the dedicatee of something (e.g., a work, object, or honor) or serves as an alternative name or nickname for another entity.
-
D.
usesNicknameOf
Indicates that one entity refers to another entity by a nickname derived from or associated with that other entity’s name.
-
E.
usesNicknameFor
Indicates that one entity habitually refers to another entity by a nickname rather than their formal or given name.
- F. None of above.
Provenance (3 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa3fb3d88190b5878cadf6125c31 |
completed | May 3, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.