Triple
T2559789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgian Cup |
E57214
|
entity |
| Predicate | domesticCupLevel |
P40471
|
FINISHED |
| Object | primary national cup |
—
|
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: primary national cup | Statement: [Georgian Cup, domesticCupLevel, primary national cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domesticCupLevel Context triple: [Georgian Cup, domesticCupLevel, primary national cup]
-
A.
domesticCup
Indicates that an entity has won or participated in a domestic (national-level) cup competition within its sport or domain.
-
B.
domesticCupQualifierFor
Indicates that a team has qualified for participation in a domestic cup competition.
-
C.
domesticCupHierarchyPosition
Indicates the relative ranking or level of a team or participant within the structure or tiers of a domestic cup competition.
-
D.
cupCompetition
Indicates a competitive event or tournament, typically in a knockout or cup format, held between teams or individuals.
-
E.
domesticLeagueTitle
Indicates that an entity has won a championship title in its primary national (domestic) league competition.
- F. None of above. chosen
Provenance (4 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0caeb488190b0dd8e48d0f2777d |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd35b216881908f4ef32d1c1e5080 |
completed | March 7, 2026, 7:27 a.m. |
Created at: March 6, 2026, 9:48 p.m.