Triple
T24684740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City Subway 2 line |
E611249
|
entity |
| Predicate | runsExpressIn |
P156972
|
FINISHED |
| Object | The Bronx |
—
|
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: The Bronx | Statement: [New York City Subway 2 line, runsExpressIn, The Bronx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsExpressIn Context triple: [New York City Subway 2 line, runsExpressIn, The Bronx]
-
A.
runsExpressIn
chosen
Indicates that one entity operates or provides an express (fast, limited-stop) service within, through, or between specified locations.
-
B.
runsVia
Indicates that a process, operation, or connection is executed, routed, or carried out through a specified intermediate channel, path, or mechanism.
-
C.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
D.
runsDirectlyOver
Indicates that one entity passes or extends immediately above another along its length or span, without significant vertical separation or intervening structures.
-
E.
runsMostly
Indicates that an entity performs running as its primary or most frequent activity compared to other activities.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:17 a.m.