Triple
T37831681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | METRO D Line |
E943218
|
entity |
| Predicate | replacedLocalRouteFrequency |
P35198
|
FINISHED |
| Object | Route 5 local bus on core corridor |
—
|
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: Route 5 local bus on core corridor | Statement: [METRO D Line, replacedLocalRouteFrequency, Route 5 local bus on core corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedLocalRouteFrequency Context triple: [METRO D Line, replacedLocalRouteFrequency, Route 5 local bus on core corridor]
-
A.
replacedFrequency
chosen
Indicates how often one entity is substituted for or takes the place of another over a given period.
-
B.
replacedLocalTimesIn
Indicates that one entity has substituted or updated the local time values within another entity or context.
-
C.
transitFrequencyApprox
Indicates an approximate rate or regularity with which a transit event or service occurs between entities.
-
D.
suggestsFrequencyNear
Indicates that one entity proposes or implies an approximate or nearby frequency value relative to another entity.
-
E.
replacesRoute
Indicates that one route supersedes or takes the place of another 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:19 p.m.