Triple
T3626403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hughie Jennings |
E76848
|
entity |
| Predicate | managerialStyle |
P4839
|
FINISHED |
| Object | fiery |
—
|
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: fiery | Statement: [Hughie Jennings, managerialStyle, fiery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managerialStyle Context triple: [Hughie Jennings, managerialStyle, fiery]
-
A.
hasDecisionMakingStyle
Indicates that an entity possesses or exhibits a particular way or pattern of making decisions.
-
B.
notableWorkStyle
Indicates a stylistic characteristic or distinctive manner associated with a notable work created by the subject.
-
C.
governingStyleAssociatedWith
Indicates a relationship where a particular governing style, method, or approach is linked or attributed to a specific entity (such as a leader, regime, or organization).
-
D.
managementApproach
chosen
Indicates the strategy, methods, or style used to direct, organize, and oversee the activities or resources of an entity or process.
-
E.
hasTypeOfLeadership
Indicates that an entity possesses or is characterized by a specific style or form of leadership.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2dc011c8190a6596f4b483fb078 |
completed | March 8, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.