Triple
T8615691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L |
E204029
|
entity |
| Predicate | primaryManhattanStreet |
P959
|
FINISHED |
| Object | 14th Street |
—
|
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: 14th Street | Statement: [L, primaryManhattanStreet, 14th Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryManhattanStreet Context triple: [L, primaryManhattanStreet, 14th Street]
-
A.
primaryAvenueInManhattan
Indicates that one entity is the main or most significant avenue located within Manhattan in relation to the other entity.
-
B.
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.
-
C.
hasStreet
chosen
Indicates that an entity is located on, associated with, or identified by a particular street.
-
D.
isNumberedAvenueOf
Indicates that one entity is an avenue identified by a numerical designation that belongs to or is part of the other entity (such as a city or road network).
-
E.
ManhattanPortalLocatedIn
Indicates that a specific portal or gateway is situated within the geographic area of Manhattan.
- 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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc4703b57c81909511de72fa5c38d7 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.