Triple
T27464302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulsanne Straight |
E693133
|
entity |
| Predicate | circuitSectionOrder |
P15216
|
FINISHED |
| Object | precedes Mulsanne Corner on a lap of Le Mans |
—
|
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: precedes Mulsanne Corner on a lap of Le Mans | Statement: [Mulsanne Straight, circuitSectionOrder, precedes Mulsanne Corner on a lap of Le Mans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circuitSectionOrder Context triple: [Mulsanne Straight, circuitSectionOrder, precedes Mulsanne Corner on a lap of Le Mans]
-
A.
circuitSection
Indicates that one entity is a specific section or segment within a larger circuit.
-
B.
circuitDirection
Indicates the orientation or flow direction of a circuit or circuit path relative to its components or layout.
-
C.
belongsToCircuitNumbering
Indicates that an entity is associated with, or assigned to, a specific circuit numbering scheme or identifier.
-
D.
componentOrder
chosen
Indicates the relative sequence or arrangement of components within a larger structure or system.
-
E.
confersOrder
Indicates that one entity formally bestows or grants an order, rank, or honorific distinction upon 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62dfbe6508190a6871084c5afe20f |
completed | May 2, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 12:51 p.m.