Triple
T30965461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ray Evernham |
E788938
|
entity |
| Predicate | workedWithManufacturer |
P42639
|
FINISHED |
| Object | Chevrolet |
—
|
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: Chevrolet | Statement: [Ray Evernham, workedWithManufacturer, Chevrolet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workedWithManufacturer Context triple: [Ray Evernham, workedWithManufacturer, Chevrolet]
-
A.
usedManufacturer
Indicates that an entity has employed or sourced products, components, or services from a particular manufacturer.
-
B.
hasWorkedOnBrand
Indicates that an entity has performed work, tasks, or services related to a particular brand.
-
C.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
D.
workedWithResource
Indicates that an entity has used, handled, or collaborated with a particular resource in the course of some activity or process.
-
E.
formerManufacturerPartner
chosen
Indicates that two entities were previously in a manufacturer–partner business relationship, but that partnership has since ended.
- 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_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:54 p.m.