Triple
T28683068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NXST |
E726057
|
entity |
| Predicate | associatedWithHeadquartersCountry |
P26640
|
FINISHED |
| Object | United States |
E14
|
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: United States | Statement: [NXST, associatedWithHeadquartersCountry, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithHeadquartersCountry Context triple: [NXST, associatedWithHeadquartersCountry, United States]
-
A.
associatedWithCompanyHeadquarters
Indicates that an entity has a relationship or connection to the headquarters location of a specific company.
-
B.
hasParentInstitutionHeadquartersIn
Indicates that the headquarters of an entity’s parent institution is located in a specified place.
-
C.
organizationHeadquarteredInCountry
chosen
Indicates that an organization’s main headquarters or principal place of business is located within a specified country.
-
D.
hasOperatorHeadquartersIn
Indicates that the primary operational headquarters of an operator is located in a specified place.
-
E.
isHeadOfficeOf
Indicates that one entity serves as the main or central administrative office for another entity, typically overseeing its operations or branches.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a01ade363088190b3a3e3dedabd1aa2 |
completed | May 11, 2026, 10:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24ec1eb5988190987ed54271f8bad2 |
completed | June 7, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_6a01acf3c5788190932bd8fcf27c123d |
completed | May 11, 2026, 10:18 a.m. |
Created at: April 28, 2026, 5:10 a.m.