Triple
T38208643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Next Alt |
E1009275
|
entity |
| Predicate | roleInAlticeGroup |
P80878
|
FINISHED |
| Object | ultimate holding company |
—
|
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: ultimate holding company | Statement: [Next Alt, roleInAlticeGroup, ultimate holding company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAlticeGroup Context triple: [Next Alt, roleInAlticeGroup, ultimate holding company]
-
A.
roleAtWorldCom
Indicates that an entity holds or held a specific role or position at the company WorldCom.
-
B.
agencyRole
Indicates that one entity serves in a specific functional or organizational capacity on behalf of, or within, another entity (such as an agency, institution, or governing body).
-
C.
portfolioRole
chosen
Indicates the specific function, capacity, or position an entity holds within a portfolio or collection of assets.
-
D.
roleInEHT
Indicates that an entity holds a specific role or function within the Event Horizon Telescope (EHT) collaboration or project.
-
E.
roleInSkyline
Indicates that an entity has a specific role or function within the composition or appearance of a skyline.
- 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a03232efd8481908ee25447a29ee20b |
completed | May 12, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_6a032269dcb08190907c965c28145b77 |
completed | May 12, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:30 p.m.