Triple
T2977192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bathurst 1000 |
E80425
|
entity |
| Predicate | typicalEntryType |
P44366
|
FINISHED |
| Object | two‑driver teams |
—
|
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: two‑driver teams | Statement: [Bathurst 1000, typicalEntryType, two‑driver teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEntryType Context triple: [Bathurst 1000, typicalEntryType, two‑driver teams]
-
A.
typicalCoreType
Indicates that something is a standard or characteristic core type within a given classification or system.
-
B.
typicalSegmentType
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
-
C.
typicalKey
Indicates that the referenced key is the standard or most commonly used key associated with an entity or context.
-
D.
typicalUnitType
Indicates that one entity is the standard or commonly used unit type associated with measuring or expressing the other entity.
-
E.
typicalEntryRoute
Indicates the usual or most common path or method by which something is entered or accessed.
- F. None of above. chosen
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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad998c589c8190b4530f3fb8975187 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:58 p.m.