Triple
T23818457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Avenue–149th Street |
E589160
|
entity |
| Predicate | entrance |
P6140
|
FINISHED |
| Object | Third Avenue and East 149th Street |
—
|
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: Third Avenue and East 149th Street | Statement: [Third Avenue–149th Street, entrance, Third Avenue and East 149th Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entrance Context triple: [Third Avenue–149th Street, entrance, Third Avenue and East 149th Street]
-
A.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
-
B.
hasEntrance
chosen
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
C.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
D.
entranceOrientation
Indicates the directional orientation or facing direction of an entrance relative to a reference frame or environment.
-
E.
entranceSize
Indicates the size or dimensions of an entrance relative to a referenced object or structure.
- 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_69e25d18619081909c7fb89d8926f14a |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7ad0ec88190bace5c3f00908b30 |
completed | April 29, 2026, 8:56 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:58 p.m.