Triple
T4013418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L’Étape du Tour |
E90698
|
entity |
| Predicate | raceConditions |
P22542
|
FINISHED |
| Object | closed roads |
—
|
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: closed roads | Statement: [L’Étape du Tour, raceConditions, closed roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceConditions Context triple: [L’Étape du Tour, raceConditions, closed roads]
-
A.
requiresConcurrenceWith
Indicates that one action, decision, or condition must be agreed upon or approved by another specified party or entity before it can proceed or be valid.
-
B.
raceMeeting
Indicates a competitive event where multiple participants race against each other under shared rules and conditions.
-
C.
heldConcurrentlyWith
Indicates that two or more events, roles, or states occurred or were in effect at the same time.
-
D.
parallelEvent
Indicates that two or more events occur at the same time or overlap in time without a required order between them.
-
E.
conditions
chosen
Indicates that one entity specifies or imposes requirements, constraints, or circumstances that must be satisfied or hold true for another entity or situation.
- 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_69aed95e44088190aff7d90a151b1b20 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.