Triple
T13209223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Rapid |
E314443
|
entity |
| Predicate | corridorTypeServed |
P2566
|
FINISHED |
| Object | major transit corridors |
—
|
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: major transit corridors | Statement: [Metro Rapid, corridorTypeServed, major transit corridors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corridorTypeServed Context triple: [Metro Rapid, corridorTypeServed, major transit corridors]
-
A.
corridorType
Indicates the specific kind or classification of a corridor associated with an entity or location.
-
B.
primaryCorridorServed
Indicates that a corridor is the main route or pathway served by a given service, facility, or entity.
-
C.
isPartOfCorridorSystem
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
-
D.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
E.
hasServiceOnCorridor
chosen
Indicates that a service operates along, or is provided on, a specific corridor or 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9e072c8190b66e2c2430628ed0 |
completed | April 10, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:17 p.m.