Triple
T27775753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oceania Women’s Football Championship |
E699179
|
entity |
| Predicate | tournamentRole |
P33874
|
FINISHED |
| Object | regional championship |
—
|
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: regional championship | Statement: [Oceania Women’s Football Championship, tournamentRole, regional championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentRole Context triple: [Oceania Women’s Football Championship, tournamentRole, regional championship]
-
A.
competitionRole
chosen
Indicates that an entity holds a specific role, position, or function within a competitive event or contest.
-
B.
tourRole
Indicates the specific function, capacity, or responsibility an entity has within the context of a tour.
-
C.
leagueSystemRole
Indicates the specific role or function an entity holds within a league’s organizational or competitive system.
-
D.
lineupRole
Indicates the specific role or position an entity holds within a lineup or ordered group.
-
E.
roleInRacingCalendar
Indicates the specific function or significance that a race or event holds within the overall racing calendar or season schedule.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 5:05 p.m.