Triple
T24965934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 86th Street |
E624741
|
entity |
| Predicate | entrancesOn |
P1974
|
FINISHED |
| Object | West 86th Street |
E361273
|
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: West 86th Street | Statement: [86th Street, entrancesOn, West 86th Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entrancesOn Context triple: [86th Street, entrancesOn, West 86th Street]
-
A.
hasEntranceOn
chosen
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
B.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
C.
hasNumberOfEntrances
Indicates the relationship that specifies how many entrances an entity possesses.
-
D.
hasEntranceStructure
Indicates that one entity possesses or is associated with a specific physical structure that serves as its entrance.
-
E.
hasSeparateEntrances
Indicates that the related entities each have their own distinct entrance, rather than sharing a common one.
- F. None of above.
Provenance (4 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a11853d2ff48190b7b9899eb45af45b |
completed | May 23, 2026, 10:45 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6 a.m.