Triple
T31966896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TBS Broadcasting Center |
E816200
|
entity |
| Predicate | parentOrganizationHeadquartered |
P191105
|
FINISHED |
| Object | TBS Holdings |
—
|
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: TBS Holdings | Statement: [TBS Broadcasting Center, parentOrganizationHeadquartered, TBS Holdings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentOrganizationHeadquartered Context triple: [TBS Broadcasting Center, parentOrganizationHeadquartered, TBS Holdings]
-
A.
hasOrganizationHeadquartered
Indicates that an organization has its main headquarters located in a specified place.
-
B.
organizationTypeHeadquartered
Indicates that an organization of a specified type has its headquarters located in a particular place.
-
C.
hasOrganizationHeadquarters
Indicates that an organization’s main administrative or operational center is located at a specific place.
-
D.
parentOrganization
Indicates that one organization is the higher-level or owning entity in an organizational hierarchy relative to another organization.
-
E.
organisationHeadquartered
Indicates that an organisation has its main headquarters located in a specified place.
- F. None of above. chosen
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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcda35dc048190a3c90e15230900e0 |
completed | May 7, 2026, 6:30 p.m. |
Created at: May 1, 2026, 12:10 a.m.