Triple
T12257938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COSAFA Cup |
E292148
|
entity |
| Predicate | eligibleTeamsRegion |
P104089
|
FINISHED |
| Object | COSAFA member associations |
—
|
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: COSAFA member associations | Statement: [COSAFA Cup, eligibleTeamsRegion, COSAFA member associations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleTeamsRegion Context triple: [COSAFA Cup, eligibleTeamsRegion, COSAFA member associations]
-
A.
eligibleTeamsFrom
Indicates that certain teams qualify or are allowed to originate from a specified source, context, or selection criteria.
-
B.
regionTeam
Indicates that a team is associated with, operates in, or represents a specific geographic region.
-
C.
teamSportGoverningBodyRegion
Indicates the geographic region or jurisdiction within which a governing body oversees or regulates a particular team sport.
-
D.
teamRegion
Indicates that a team is associated with, based in, or represents a particular geographic region.
-
E.
eligibleLeague
Indicates that an entity (such as a team or player) is qualified or permitted to participate in a particular league.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d93805cee08190a532ebcf5908e617 |
completed | April 10, 2026, 5:48 p.m. |
Created at: April 8, 2026, 9:52 p.m.