Triple
T22690857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Video Assistant Referee system |
E561045
|
entity |
| Predicate | reviewPrinciple |
P33073
|
FINISHED |
| Object | clear and obvious error |
—
|
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: clear and obvious error | Statement: [Video Assistant Referee system, reviewPrinciple, clear and obvious error]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reviewPrinciple Context triple: [Video Assistant Referee system, reviewPrinciple, clear and obvious error]
-
A.
principleClarified
Indicates that a principle has been made clearer or more explicit, typically by explanation, refinement, or elaboration.
-
B.
principle6
Indicates that one entity upholds, follows, or is governed by a specific sixth principle in a defined set of principles.
-
C.
principle7
Indicates that an entity is associated with, governed by, or exemplifies the seventh principle in a defined set of principles.
-
D.
principle1
Indicates that one entity serves as a primary rule, guideline, or foundational principle governing or guiding another entity.
-
E.
testsPrinciple
chosen
Indicates that an entity evaluates, examines, or challenges the validity or applicability of a principle.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789adcc48190b4a717166d5dba19 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.