Triple
T38208619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Next Alt |
E1009275
|
entity |
| Predicate | hasPrimaryShareholder |
P204533
|
FINISHED |
| Object | Patrick Drahi |
E64543
|
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: Patrick Drahi | Statement: [Next Alt, hasPrimaryShareholder, Patrick Drahi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryShareholder Context triple: [Next Alt, hasPrimaryShareholder, Patrick Drahi]
-
A.
hasShareholdersFrom
Indicates that an entity has shareholders who originate from or are associated with a specified country, region, or organization.
-
B.
canHaveMultipleShareholders
Indicates that an entity is permitted to have more than one shareholder at the same time.
-
C.
canHaveSingleShareholder
Indicates that an entity is legally permitted to be owned or constituted with only one shareholder.
-
D.
hasMajorShareholderHistory
Indicates that an entity has had one or more major shareholders at some point in its history.
-
E.
majorShareholderOf
Indicates that one entity owns a controlling or significantly large portion of another entity’s shares or equity.
- F. None of above. chosen
Provenance (5 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_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41a7d3dc8c8190a15807a0be7dbe97 |
completed | June 28, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:30 p.m.