Triple
T9584309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 191st Street (IRT Broadway–Seventh Avenue Line) |
E231248
|
entity |
| Predicate | pedestrianTunnelLength |
P12895
|
FINISHED |
| Object | approximately 900 feet |
—
|
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: approximately 900 feet | Statement: [191st Street (IRT Broadway–Seventh Avenue Line), pedestrianTunnelLength, approximately 900 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pedestrianTunnelLength Context triple: [191st Street (IRT Broadway–Seventh Avenue Line), pedestrianTunnelLength, approximately 900 feet]
-
A.
hasTunnelLengthApprox
chosen
Indicates that an entity has a tunnel whose length is approximately a specified value.
-
B.
hasRailwayTunnel
Indicates that one entity contains, includes, or is connected by a railway tunnel associated with the other entity.
-
C.
numberOfMajorTunnels
Indicates the count of primary or significant tunnels associated with an entity.
-
D.
hasPromenadeLength
Indicates the length or extent of a promenade associated with an entity.
-
E.
undergroundCavernLength
Indicates the measured linear extent or distance from one end to the other of an underground cavern.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99d080c88190a7d3876589d7b864 |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:06 p.m.