Triple
T24284581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4 × 100 metres relay |
E605635
|
entity |
| Predicate | commonBatonTechnique |
P68189
|
FINISHED |
| Object | blind pass |
—
|
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: blind pass | Statement: [4 × 100 metres relay, commonBatonTechnique, blind pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonBatonTechnique Context triple: [4 × 100 metres relay, commonBatonTechnique, blind pass]
-
A.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
B.
allowedTechnique
chosen
Indicates that a particular technique or method is permitted or acceptable to use in a given context or under specified rules.
-
C.
batType
Indicates the specific category or kind of bat that an entity belongs to.
-
D.
methodOfCombat
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
-
E.
bantamUse
Indicates that one entity uses, employs, or makes use of another entity in a small-scale, lightweight, or limited-capacity manner.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f54c5948190a28207d47d6205e4 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.