Triple
T23389577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Jensen |
E593974
|
entity |
| Predicate | powerLevelInStory |
P152071
|
FINISHED |
| Object | controls the board of the conglomerate that owns UBS |
—
|
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: controls the board of the conglomerate that owns UBS | Statement: [Arthur Jensen, powerLevelInStory, controls the board of the conglomerate that owns UBS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerLevelInStory Context triple: [Arthur Jensen, powerLevelInStory, controls the board of the conglomerate that owns UBS]
-
A.
powerLevel
Indicates the degree or intensity of power or strength possessed by an entity in a given context.
-
B.
powerLevelVariesBy
Indicates that the power level of an entity changes depending on, or as a function of, another specified factor or context.
-
C.
powerCharacter
Indicates that one entity possesses, controls, or exerts power or influence over another entity.
-
D.
heroPower
Indicates that an entity possesses or is associated with a particular heroic power or special ability.
-
E.
spellLevel
Indicates the level or rank assigned to a spell within a spellcasting or magic system.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a49a7c14819082aab826715976c5 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:35 p.m.