Triple
T418859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discovery, Inc. (regional operations) |
E8054
|
entity |
| Predicate | corporateStructureRole |
P8439
|
FINISHED |
| Object | regional management hub |
—
|
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: regional management hub | Statement: [Discovery, Inc. (regional operations), corporateStructureRole, regional management hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corporateStructureRole Context triple: [Discovery, Inc. (regional operations), corporateStructureRole, regional management hub]
-
A.
corporateStructure
Indicates how entities are organized, controlled, and related within a corporate hierarchy or ownership structure.
-
B.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
C.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
D.
officeHierarchy
Indicates a reporting or supervisory relationship between positions within an office, defining who is above or below whom in the organizational chain of command.
-
E.
roleInIndustry
chosen
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd1ca148190a66bd8c5aad867d5 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.