Triple
T31844901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J (New York City Subway service) |
E812910
|
entity |
| Predicate | serviceAreaNeighborhood |
P4813
|
FINISHED |
| Object | Lower Manhattan |
—
|
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: Lower Manhattan | Statement: [J (New York City Subway service), serviceAreaNeighborhood, Lower Manhattan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceAreaNeighborhood Context triple: [J (New York City Subway service), serviceAreaNeighborhood, Lower Manhattan]
-
A.
hasNeighbourhood
chosen
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
B.
neighborhood
Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
-
C.
serviceAreaName
Indicates the designated name of the geographic or functional area that a service covers or operates within.
-
D.
partOfNeighborhoodNetwork
Indicates that an entity belongs to, or is included within, a specific neighborhood’s interconnected network or system.
-
E.
accessesNeighborhood
Indicates that one entity has the ability or permission to enter, reach, or make use of a particular neighborhood.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 30, 2026, 11:50 p.m.