Triple
T1602914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Futsal Champions League |
E34434
|
entity |
| Predicate | substitutionRule |
P28179
|
FINISHED |
| Object | flying substitutions |
—
|
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: flying substitutions | Statement: [UEFA Futsal Champions League, substitutionRule, flying substitutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: substitutionRule Context triple: [UEFA Futsal Champions League, substitutionRule, flying substitutions]
-
A.
compositionRule
Indicates how multiple elements or components are combined or arranged according to a specific rule or pattern.
-
B.
typicalRuleModification
Indicates a change made to a standard or default rule, adjusting how that rule normally applies or operates.
-
C.
usesRulesFrom
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
D.
setsRulesFor
Indicates that one entity establishes or defines rules, guidelines, or constraints that another entity is expected to follow.
-
E.
mayBeReplacedBy
chosen
Indicates that one entity can potentially be substituted or superseded 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a95b02cd448190be8e3db9a5a7bac0 |
completed | March 5, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69a907c1cad08190b9728dd557f39aa0 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.