Triple
T6643905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dynamo Tbilisi |
E150651
|
entity |
| Predicate | currentLeagueSystem |
P8322
|
FINISHED |
| Object | Georgian football league system |
—
|
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: Georgian football league system | Statement: [Dynamo Tbilisi, currentLeagueSystem, Georgian football league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentLeagueSystem Context triple: [Dynamo Tbilisi, currentLeagueSystem, Georgian football league system]
-
A.
countryLeagueSystem
Indicates that a particular league system operates within, or is associated with, a specific country.
-
B.
typeOfLeagueSystem
chosen
Indicates that one entity is the kind or structure of league system to which another entity belongs or in which it operates.
-
C.
leagueType
Indicates the classification or category of a league within a broader organizational or competitive structure.
-
D.
stateLeague
Indicates that a sports team or club competes in, or is affiliated with, a particular state-level league or competition.
-
E.
hasSeparateLeagueSystemFor
Indicates that one entity organizes or maintains a distinct, independent league structure specifically for another entity or group.
- 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 p.m.