Triple
T38358778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 9 Hours of Kyalami |
E1046408
|
entity |
| Predicate | circuitLayoutType |
P167286
|
FINISHED |
| Object | permanent road course |
—
|
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: permanent road course | Statement: [9 Hours of Kyalami, circuitLayoutType, permanent road course]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circuitLayoutType Context triple: [9 Hours of Kyalami, circuitLayoutType, permanent road course]
-
A.
hasCircuitLayoutType
chosen
Indicates that an entity is associated with or characterized by a specific type or category of circuit layout.
-
B.
hasCircuitLayout
Indicates that one entity possesses, includes, or is associated with a specific circuit layout design of another entity.
-
C.
circuitType
Indicates the specific kind or category of electrical circuit associated with an entity.
-
D.
typeOfCircuit
Indicates that one entity is classified as a specific kind or category of electrical circuit represented by the other entity.
-
E.
typicalCircuitType
Indicates that one entity is the usual or standard type of circuit associated with 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_69f76e3a94fc81908edc175e8d259e80 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcc7a4d7f881908b43b960911b81e9 |
completed | May 7, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69fcc589720c819089c8f500fea3c86a |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:31 p.m.