Triple
T7488069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Army Plaza (Central Park) |
E176931
|
entity |
| Predicate | hasStreetAddressApprox |
P959
|
FINISHED |
| Object | Fifth Avenue and East 59th 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: Fifth Avenue and East 59th Street | Statement: [Grand Army Plaza (Central Park), hasStreetAddressApprox, Fifth Avenue and East 59th Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetAddressApprox Context triple: [Grand Army Plaza (Central Park), hasStreetAddressApprox, Fifth Avenue and East 59th Street]
-
A.
hasStreet
chosen
Indicates that an entity is located on, associated with, or identified by a particular street.
-
B.
streetAddress
Indicates the specific location of an entity in terms of its numbered building and street name within a postal address.
-
C.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
D.
hasNearbyStreet
Indicates that one entity is located close to or adjacent to a street.
-
E.
locationAddressed
Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
- 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f55965ac81909d3c3a5422b22d44 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:43 p.m.