Triple
T11711703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgian football league system |
E278387
|
entity |
| Predicate | includesYouthCompetitions |
P80774
|
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: [Georgian football league system, includesYouthCompetitions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesYouthCompetitions Context triple: [Georgian football league system, includesYouthCompetitions, yes]
-
A.
includesYouthLeagues
chosen
Indicates that the subject entity offers, contains, or is associated with organized leagues or programs specifically for youth participants.
-
B.
includesCompetition
Indicates that one entity contains, features, or encompasses a competition as part of its scope or content.
-
C.
juniorEventsIncluded
Indicates that events involving junior participants or categories are included within a given set, schedule, or scope.
-
D.
eligibleCompetition
Indicates that an entity meets the required conditions to participate in a particular competition.
-
E.
qualifyingCompetitionFor
Indicates that one competition serves as a qualifying event for participation in another competition.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4be10088190854699385d1f6a95 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7d483081909c2a101087515d74 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.