Triple
T35359319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hall of Fame Racing |
E1021427
|
entity |
| Predicate | usedEngineSupplier |
P17328
|
FINISHED |
| Object | Joe Gibbs Racing engines |
—
|
LITERAL 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: Joe Gibbs Racing engines | Statement: [Hall of Fame Racing, usedEngineSupplier, Joe Gibbs Racing engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedEngineSupplier Context triple: [Hall of Fame Racing, usedEngineSupplier, Joe Gibbs Racing engines]
-
A.
previouslyUsedEngine
Indicates that an engine has been used before in a prior context or application, rather than being new or unused.
-
B.
engineSupplier
chosen
Indicates a relationship where one entity supplies or provides engines to another entity.
-
C.
testedEngine
Indicates that an engine has undergone a testing process to evaluate its performance, functionality, or reliability.
-
D.
usedManufacturer
Indicates that an entity has employed or sourced products, components, or services from a particular manufacturer.
-
E.
firstStageEngineSupplier
Indicates that one entity serves as the supplier of the first-stage engine for another entity, typically a launch vehicle or rocket.
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.