Triple
T11333806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Success, New York |
E268415
|
entity |
| Predicate | UNHeadquartersFrom |
P17490
|
FINISHED |
| Object | 1946 |
—
|
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: 1946 | Statement: [Lake Success, New York, UNHeadquartersFrom, 1946]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNHeadquartersFrom Context triple: [Lake Success, New York, UNHeadquartersFrom, 1946]
-
A.
headquartersFunction
Indicates that an entity serves as the main administrative or central operating location (headquarters) for another entity.
-
B.
headquartersFor
chosen
Indicates that a location serves as the main administrative center or base of operations for an organization or entity.
-
C.
isBlockHeadquartersOf
Indicates that a particular block serves as the main headquarters location for a specified entity.
-
D.
zoneHeadquarter
Indicates that an entity serves as the main administrative or coordinating headquarters for a specified zone or region.
-
E.
headquartersDuringSelection
Indicates that an entity serves as the headquarters of another entity specifically during a defined selection period or selection process.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9fe5d5881908d786b212a554d8b |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:33 p.m.