Triple
T24832929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 12 Hours of Sebring |
E621387
|
entity |
| Predicate | circuitBuiltOn |
P2012
|
FINISHED |
| Object | former Hendricks Army Airfield |
—
|
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: former Hendricks Army Airfield | Statement: [12 Hours of Sebring, circuitBuiltOn, former Hendricks Army Airfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circuitBuiltOn Context triple: [12 Hours of Sebring, circuitBuiltOn, former Hendricks Army Airfield]
-
A.
circuitUsed
Indicates that a particular circuit is utilized or employed in performing an action, process, or function.
-
B.
builtOn
chosen
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
C.
typicallyBuiltAt
Indicates the usual or most common location, context, or time at which something is constructed or created.
-
D.
circuitDesigner
Indicates that an entity is responsible for designing or creating electronic circuits for another entity or system.
-
E.
circuit
Indicates that one entity forms or participates in an electrical or logical pathway that allows current or signals to flow through a connected system involving another entity.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:16 a.m.