Triple
T12827278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Riggins |
E306686
|
entity |
| Predicate | managingStyle |
P4839
|
FINISHED |
| Object | old-school |
—
|
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: old-school | Statement: [Joe Riggins, managingStyle, old-school]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managingStyle Context triple: [Joe Riggins, managingStyle, old-school]
-
A.
hasDecisionMakingStyle
Indicates that an entity possesses or exhibits a particular way or pattern of making decisions.
-
B.
managementApproach
chosen
Indicates the strategy, methods, or style used to direct, organize, and oversee the activities or resources of an entity or process.
-
C.
managementIs
Indicates that one entity holds a managerial role, responsibility, or authority over another entity.
-
D.
notableWorkStyle
Indicates a stylistic characteristic or distinctive manner associated with a notable work created by the subject.
-
E.
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).
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa08cd481909a946046ba63809f |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:33 p.m.