Triple
T261479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Plaza |
E5549
|
entity |
| Predicate | hasPostalAddress |
P4379
|
FINISHED |
| Object | United Nations Plaza, New York, NY 10017 |
—
|
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: United Nations Plaza, New York, NY 10017 | Statement: [United Nations Plaza, hasPostalAddress, United Nations Plaza, New York, NY 10017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostalAddress Context triple: [United Nations Plaza, hasPostalAddress, United Nations Plaza, New York, NY 10017]
-
A.
hasAddress
chosen
Indicates that an entity is associated with a specific address or location.
-
B.
addressType
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
-
C.
hasPostalCodePrefix
Indicates that a location’s postal code begins with a specified sequence of characters.
-
D.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
E.
addresses
Indicates that one entity directs speech, communication, or written correspondence specifically toward another entity.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b6c968c819094fc903a3a377e15 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.