Triple
T15473407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I liga |
E376720
|
entity |
| Predicate | usesLeagueTableRanking |
P91092
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [I liga, usesLeagueTableRanking, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLeagueTableRanking Context triple: [I liga, usesLeagueTableRanking, yes]
-
A.
usesLeagueTable
chosen
Indicates that one entity bases its rankings, decisions, or evaluations on a structured league table of comparative standings.
-
B.
hasTableRanking
Indicates that an entity is assigned a specific position or order within a ranked table or list.
-
C.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
D.
leagueStandingDescribed
Indicates that a particular description or statement expresses or explains a team's position or ranking within a league's standings.
-
E.
usesInStandingsTables
Indicates that something is employed or applied within standings tables, such as rankings or league tables, to represent or organize comparative positions.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6c57308190b4cfe661c26addd4 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.