Triple
T12490566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League 2014–15 with Chelsea |
E298549
|
entity |
| Predicate | managerTacticalApproach |
P50132
|
FINISHED |
| Object | pragmatic |
—
|
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: pragmatic | Statement: [Premier League 2014–15 with Chelsea, managerTacticalApproach, pragmatic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managerTacticalApproach Context triple: [Premier League 2014–15 with Chelsea, managerTacticalApproach, pragmatic]
-
A.
tacticalStyle
chosen
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
-
B.
managementApproach
Indicates the strategy, methods, or style used to direct, organize, and oversee the activities or resources of an entity or process.
-
C.
tactic
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
D.
positionOnTactics
Indicates the stance or viewpoint an entity holds regarding a particular tactic or set of tactics.
-
E.
strategyType
Indicates the specific kind or category of strategy associated with an entity or action.
- 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e8a706c8190873623eab7db607d |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d41f3cc8190a3331fb9a895306f |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.