Triple
T16212470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kansas Highway 1 (Metcalf Avenue corridor nearby) |
E393499
|
entity |
| Predicate | hasCorridorName |
P122190
|
FINISHED |
| Object | Metcalf Avenue |
—
|
NE NERFINISHED |
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: Metcalf Avenue | Statement: [Kansas Highway 1 (Metcalf Avenue corridor nearby), hasCorridorName, Metcalf Avenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorridorName Context triple: [Kansas Highway 1 (Metcalf Avenue corridor nearby), hasCorridorName, Metcalf Avenue]
-
A.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
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.
isPartOfCorridorSystem
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
- F. None of above. chosen
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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f2c1288190bfaed49c364bfa22 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:03 a.m.