Triple
T30965460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ray Evernham |
E788938
|
entity |
| Predicate | workedWithDriver |
P103677
|
FINISHED |
| Object | Jeff Gordon |
—
|
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: Jeff Gordon | Statement: [Ray Evernham, workedWithDriver, Jeff Gordon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workedWithDriver Context triple: [Ray Evernham, workedWithDriver, Jeff Gordon]
-
A.
associatedWithDriver
chosen
Indicates that one entity has a connection or relationship with a specific driver, such as being linked, assigned, or otherwise related to that driver.
-
B.
alsoAssociatedWithDriver
Indicates that an entity has an additional or secondary association with a specified driver, beyond any primary or previously stated driver relationship.
-
C.
hasFormerDriver
Indicates that an entity previously served as a driver for another entity but no longer holds that role.
-
D.
isDriven
Indicates that one entity operates or controls the movement of another entity, typically a vehicle or device.
-
E.
workedWithResource
Indicates that an entity has used, handled, or collaborated with a particular resource in the course of some activity or process.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:54 p.m.