Triple
T7152709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 22nd Street |
E166729
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | 22nd Street |
E166729
|
NE 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: 22nd Street | Statement: [22nd Street, hasName, 22nd Street]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 22nd Street Context triple: [22nd Street, hasName, 22nd Street]
-
A.
22nd Street
chosen
22nd Street is a street that lends its name to the nearby 22nd Street station, serving as a local thoroughfare in its area.
-
B.
2nd Street
2nd Street is a major east–west thoroughfare in downtown Los Angeles that runs through the historic Little Tokyo neighborhood and connects several key districts in the city.
-
C.
North 2nd Street
North 2nd Street is a city thoroughfare that serves as part of the numbered street grid in its urban area.
-
D.
20th Street
20th Street is an east–west thoroughfare in Manhattan, New York City, running through neighborhoods including the Flatiron District.
-
E.
25th Street
25th Street is a local New York City Subway station in Brooklyn serving the BMT Fourth Avenue Line.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f52c1081908c4fa424d5e965bc |
completed | March 27, 2026, 8:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7adad45208190a8e09173a4d26591 |
completed | March 28, 2026, 10:30 a.m. |
Created at: March 27, 2026, 2:46 p.m.