Triple
T9047249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian football league system |
E216784
|
entity |
| Predicate | matchResultDetermination |
P6592
|
FINISHED |
| Object | points total in league table |
—
|
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: points total in league table | Statement: [Russian football league system, matchResultDetermination, points total in league table]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchResultDetermination Context triple: [Russian football league system, matchResultDetermination, points total in league table]
-
A.
matchResult
Indicates the outcome or final status produced by a particular match or game between participants.
-
B.
resultDetermination
chosen
Indicates the process or criteria by which an outcome, decision, or result is established or concluded from given inputs or conditions.
-
C.
matchResultInfluenced
Indicates that the outcome of a match was affected or altered by a specified factor, event, or condition.
-
D.
matchType
Indicates the specific category or nature of how two or more entities correspond or align with each other within a given context.
-
E.
matchStructure
Indicates that two entities share the same structural pattern or organization, regardless of their specific content or values.
- 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b5022c88190ab6b6de3c3830a41 |
completed | April 1, 2026, 12:48 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:09 p.m.