Triple
T25062660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BART Antioch extension corridor |
E627702
|
entity |
| Predicate | corridorNameUsedBy |
P122190
|
FINISHED |
| Object | BART planning documents |
—
|
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: BART planning documents | Statement: [BART Antioch extension corridor, corridorNameUsedBy, BART planning documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corridorNameUsedBy Context triple: [BART Antioch extension corridor, corridorNameUsedBy, BART planning documents]
-
A.
hasCorridorName
chosen
Indicates that an entity is associated with or identified by the name of a specific corridor.
-
B.
corridorNameOrigin
Indicates that a corridor’s name is derived from, or originates in reference to, a particular source (such as a person, place, event, or feature).
-
C.
formerNameOfCorridor
Indicates that one corridor previously had a different name, which is now the current name of another corridor.
-
D.
corridorType
Indicates the specific kind or classification of a corridor associated with an entity or location.
-
E.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
- 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4599b7ff081909862edeae57c2c2d |
completed | May 1, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:10 a.m.