Triple
T16752942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Réseau express métropolitain |
E407129
|
entity |
| Predicate | minimumHeadway |
P22511
|
FINISHED |
| Object | approximately 2.5 minutes |
—
|
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: approximately 2.5 minutes | Statement: [Réseau express métropolitain, minimumHeadway, approximately 2.5 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumHeadway Context triple: [Réseau express métropolitain, minimumHeadway, approximately 2.5 minutes]
-
A.
maximumStationsPerSegment
Indicates the greatest number of stations that are allowed or can exist within a single segment.
-
B.
transitFrequencyApprox
Indicates an approximate rate or regularity with which a transit event or service occurs between entities.
-
C.
minimumDistanceRequirement
Indicates that there is a required minimum distance that must be maintained between the related entities.
-
D.
offPeakServiceFrequency_minutes
Indicates the number of minutes between successive services during off-peak periods.
-
E.
headway
chosen
Indicates the temporal or spatial separation maintained between moving entities, such as vehicles or trains, as they travel along the same route.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa282bb08190992c9b61caa7a345 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.