Triple
T1450186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herald Square |
E31271
|
entity |
| Predicate | servedBySubwayLine |
P17559
|
FINISHED |
| Object | B |
—
|
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: B | Statement: [Herald Square, servedBySubwayLine, B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedBySubwayLine Context triple: [Herald Square, servedBySubwayLine, B]
-
A.
subwayLine
Indicates that there is a subway line connection or service relationship between the referenced entities.
-
B.
subwayServices
Indicates that one entity provides or operates subway transportation services for another entity or area.
-
C.
hasMetroLine
chosen
Indicates that a location or area is served by, or connected to, a specific metro (subway) line.
-
D.
primaryManhattanLine
Indicates that one line segment or path is the main or dominant axis, measured using Manhattan (grid-based) distance, relative to other possible lines.
-
E.
bronxLine
Indicates a relationship where something is part of, associated with, or runs along the Bronx transit or route line.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c55d923c8190957756f834f94462 |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.