Triple
T378015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alan Mulally |
E8612
|
entity |
| Predicate | leadershipStyle |
P2888
|
FINISHED |
| Object | collaborative management |
—
|
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: collaborative management | Statement: [Alan Mulally, leadershipStyle, collaborative management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadershipStyle Context triple: [Alan Mulally, leadershipStyle, collaborative management]
-
A.
hasDecisionMakingStyle
chosen
Indicates that an entity possesses or exhibits a particular way or pattern of making decisions.
-
B.
leadershipPosition
Indicates that one entity holds a role of authority, guidance, or decision-making responsibility over others within an organization, group, or context.
-
C.
mainLeaders
Indicates that the referenced entities serve as the primary or most important leaders within a group, organization, or context.
-
D.
styleOfPlay
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
E.
operatorStyle
Indicates the manner or approach an operator uses to perform or manage an operation, such as their method, technique, or behavioral style in carrying out tasks.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2974988190a1d6316cbb5159c8 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e96351cc8190a55adf95f8c27e9e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.