Triple
T33837572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vodafone Group |
E867275
|
entity |
| Predicate | roleOfJeanFrançoisVanBoxmeer |
P182281
|
FINISHED |
| Object | Chairman |
—
|
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: Chairman | Statement: [Vodafone Group, roleOfJeanFrançoisVanBoxmeer, Chairman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfJeanFrançoisVanBoxmeer Context triple: [Vodafone Group, roleOfJeanFrançoisVanBoxmeer, Chairman]
-
A.
roleForDieterichBuxtehude
Indicates the specific role or position associated with Dieterich Buxtehude in a given context or work.
-
B.
roleOfWilliamVonMeister
Indicates the specific role, position, or capacity that William Von Meister holds or held in relation to another entity or context.
-
C.
Félix Kir
Indicates a relationship where an entity is associated with or named after Félix Kir, typically signifying dedication, commemoration, or attribution to this person.
-
D.
roleOfIrèneJacob
Indicates that an entity holds the role or character portrayed by Irène Jacob in a work or context.
-
E.
KarlVonMüllerRole
Indicates that an entity holds or is assigned the role or position associated with Karl von Müller.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: May 1, 2026, 1:47 a.m.