Triple
T36119857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold Coast street circuit round |
E1044712
|
entity |
| Predicate | primaryCarsUsed |
P12443
|
FINISHED |
| Object | Supercars (V8 touring cars) |
E316501
|
NE 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: Supercars (V8 touring cars) | Statement: [Gold Coast street circuit round, primaryCarsUsed, Supercars (V8 touring cars)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCarsUsed Context triple: [Gold Coast street circuit round, primaryCarsUsed, Supercars (V8 touring cars)]
-
A.
primaryCarNumberUsed
Indicates that a particular car number is the main or default one used for an entity in a given context.
-
B.
vehicleUsed
chosen
Indicates that a particular vehicle is utilized or employed in performing an action, event, or activity.
-
C.
formerCarCategories
Indicates that an entity previously belonged to certain car categories but no longer does so.
-
D.
formerCar
Indicates that one entity was previously the car of another entity but is no longer in that role.
-
E.
primaryBusinessVehicle
Indicates that one entity serves as the main or principal vehicle used for conducting the other entity’s business activities.
- F. None of above.
Provenance (4 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a390d3e5e948190b20be728f76236ac |
completed | June 22, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.