Triple
T2027757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 7 (Mexico City Metrobús) |
E44446
|
entity |
| Predicate | peakServiceLevel |
P27840
|
FINISHED |
| Object | high frequency |
—
|
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: high frequency | Statement: [Line 7 (Mexico City Metrobús), peakServiceLevel, high frequency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakServiceLevel Context triple: [Line 7 (Mexico City Metrobús), peakServiceLevel, high frequency]
-
A.
peakService
chosen
Indicates that the service is operating during its highest-demand or peak usage period.
-
B.
peakServiceOnly
Indicates that the service operates only during peak periods and is not available at off-peak times.
-
C.
serviceLevel
Indicates the degree or quality of service provided or received in the relationship between entities.
-
D.
peakStatus
Indicates the condition or phase of something at its highest or most intense point in its progression or lifecycle.
-
E.
maximumService
Indicates that an entity provides the highest allowable or achievable level of service within a given context or system.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb911e5dc819097e40af0da4d01e7 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.