Triple
T35374391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloomingdale family |
E1021863
|
entity |
| Predicate | businessHeadquarteredIn |
P76911
|
FINISHED |
| Object | New York City |
—
|
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: New York City | Statement: [Bloomingdale family, businessHeadquarteredIn, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessHeadquarteredIn Context triple: [Bloomingdale family, businessHeadquarteredIn, New York City]
-
A.
employerHeadquarters
Indicates the location where an employer’s main corporate offices or central administrative operations are based.
-
B.
headquartersOfBusiness
chosen
Indicates that a location serves as the main administrative center or principal office for a business.
-
C.
majorCompanyHeadquartered
Indicates that a company is a primary or significant corporate entity whose main headquarters is located in a specified place.
-
D.
headquarteredWith
Indicates that two entities share the same headquarters location.
-
E.
hasHeadquartersFunctionFor
Indicates that an entity serves as the central coordinating or managing headquarters for another entity’s operations or activities.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.