Triple
T23900368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Three (Greece) |
E601024
|
entity |
| Predicate | mainDomesticCup |
P53444
|
FINISHED |
| Object | Greek Football Cup |
—
|
NE NERFINISHED |
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: Greek Football Cup | Statement: [Big Three (Greece), mainDomesticCup, Greek Football Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDomesticCup Context triple: [Big Three (Greece), mainDomesticCup, Greek Football Cup]
-
A.
primaryDomesticCupStatus
chosen
Indicates the status or role of a competition as the main domestic cup within a given sports structure or country.
-
B.
domesticCupLevel
Indicates the competitive tier or stage of a team’s participation within a domestic cup competition.
-
C.
hasDomesticCupRelation
Indicates a relationship between entities based on participation, achievement, or involvement in a domestic cup competition within a country’s sports structure.
-
D.
domesticCupTitles
Indicates the number of national (in-country) cup competitions a team or club has won.
-
E.
domesticCupQualifierFor
Indicates that a team has qualified for participation in a domestic cup 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdddca088190b6c26df984a143ad |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:26 p.m.