Triple
T6648838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Other Match Officials |
E150767
|
entity |
| Predicate | decisionTypeAssisted |
P2165
|
FINISHED |
| Object | offside |
—
|
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: offside | Statement: [The Other Match Officials, decisionTypeAssisted, offside]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionTypeAssisted Context triple: [The Other Match Officials, decisionTypeAssisted, offside]
-
A.
decisionType
chosen
Indicates the specific category or nature of a decision associated with an entity or event.
-
B.
decisionMakingTool
Indicates that an entity functions as a tool or system used to support, structure, or carry out decision-making processes for another entity.
-
C.
decisionOutput
Indicates that a decision-making process produces or yields a particular outcome or result.
-
D.
decisionSplit
Indicates that a single decision point branches into multiple alternative outcomes or paths.
-
E.
decisionDirection
Indicates the orientation or course (e.g., choice, stance, or path) that a decision takes relative to available options or influencing factors.
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:01 p.m.