Triple
T38148086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn Avenue |
E952673
|
entity |
| Predicate | operatedInCorridorBy |
P30157
|
FINISHED |
| Object | Metro Transit |
E70272
|
NE 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: Metro Transit | Statement: [Penn Avenue, operatedInCorridorBy, Metro Transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInCorridorBy Context triple: [Penn Avenue, operatedInCorridorBy, Metro Transit]
-
A.
isPartOfCorridorSystem
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
-
B.
operatedAmong
chosen
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
C.
locatedInTravelDirectionCorridor
Indicates that something is positioned within a corridor that lies along the direction of travel.
-
D.
replacedInCorridorBy
Indicates that one entity has been substituted or superseded by another entity specifically within a corridor context.
-
E.
inCorridor
Indicates that one entity is located within or inside a corridor relative to another spatial context or reference.
- F. None of above.
Provenance (4 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a034af7066c81908719bff353d77b16 |
completed | May 12, 2026, 3:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a417130a8188190a01fd5b53a251a41 |
completed | June 28, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a034a2fc2308190b0b8fbd458a39323 |
completed | May 12, 2026, 3:41 p.m. |
Created at: May 3, 2026, 4:21 p.m.