Triple
T16118160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ian G. Ashken |
E391059
|
entity |
| Predicate | roleAtJarden |
P121545
|
FINISHED |
| Object | strategic leadership |
—
|
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: strategic leadership | Statement: [Ian G. Ashken, roleAtJarden, strategic leadership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtJarden Context triple: [Ian G. Ashken, roleAtJarden, strategic leadership]
-
A.
houseRole
Indicates the functional role, purpose, or use that a house has within a given context or system.
-
B.
roleAtMidway
Indicates that an entity holds or held a specific role, position, or function at the midpoint or intermediate stage of a process, event, or time period.
-
C.
roleAtVine
Indicates that an entity holds or held a specific role or position at the company Vine.
-
D.
roleInTree
Indicates the specific position or function an entity occupies within a hierarchical tree structure relative to other entities.
-
E.
roleOfPeopleOnIt
Indicates the specific roles or functions that people have in relation to a particular object, event, or context.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016c10a081909b2d23ecea153a9c |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e183b9d3f08190953ada68f4272996 |
completed | April 17, 2026, 12:50 a.m. |
Created at: April 10, 2026, 5 a.m.