Triple
T9911281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Total Football |
E185148
|
entity |
| Predicate | tacticalGoal |
P75868
|
FINISHED |
| Object | create numerical superiority around the ball |
—
|
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: create numerical superiority around the ball | Statement: [Total Football, tacticalGoal, create numerical superiority around the ball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticalGoal Context triple: [Total Football, tacticalGoal, create numerical superiority around the ball]
-
A.
tacticalPurpose
chosen
Indicates the specific tactical objective or intended operational role that an action, asset, or decision is meant to achieve within a broader plan or mission.
-
B.
tacticalOutcome
Indicates the specific result or consequence produced by a particular tactic or tactical action in a given situation.
-
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.
laterGoal
Indicates that one goal occurs or is intended to be achieved after another goal in time.
-
E.
goalType
Indicates the specific category or nature of a goal 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_69ca8296165881908ca4750701af1f29 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb512a26881908eb72a21ffb1efef |
completed | April 2, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:41 p.m.