Triple
T11150973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4 × 800 metres relay |
E263781
|
entity |
| Predicate | tacticsInvolve |
P1716
|
FINISHED |
| Object | pacing strategy for each leg |
—
|
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: pacing strategy for each leg | Statement: [4 × 800 metres relay, tacticsInvolve, pacing strategy for each leg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tacticsInvolve Context triple: [4 × 800 metres relay, tacticsInvolve, pacing strategy for each leg]
-
A.
militaryTacticsUsed
Indicates that specific military tactics are employed or applied in the context of a particular operation, conflict, or strategic situation.
-
B.
tactic
chosen
Indicates a strategic method or maneuver employed by one entity to influence, counter, or gain advantage over another in a specific context.
-
C.
tacticsManualUsedBy
Indicates that a tactics manual is utilized or applied by a particular agent or entity.
-
D.
tacticalStyle
Indicates the characteristic way in which an entity plans and executes actions or maneuvers to achieve its objectives.
-
E.
describedTactic
Indicates that one entity has provided an explanation or account of a particular tactic used or proposed by another entity.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8719e74819095413abc6c79296c |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce71944819089eee9b5c9283cbd |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.