Triple
T26398101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans-Tasman football rivalry |
E663625
|
entity |
| Predicate | confederationTeam1 |
P79226
|
FINISHED |
| Object | Asian Football Confederation |
—
|
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: Asian Football Confederation | Statement: [Trans-Tasman football rivalry, confederationTeam1, Asian Football Confederation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confederationTeam1 Context triple: [Trans-Tasman football rivalry, confederationTeam1, Asian Football Confederation]
-
A.
team1Confederation
chosen
Indicates the confederation or regional football association to which the first team in a match or comparison belongs.
-
B.
continentTeam1
Indicates that the first team is associated with or belongs to a particular continent.
-
C.
nationalTeamConfederation
Indicates the confederation or regional governing body under which a national team is organized or competes.
-
D.
continentTeam2
Indicates that the second team is associated with or belongs to a particular continent.
-
E.
hostConfederationTeam
Indicates that a team is designated as the representative (host) team of a particular confederation for an event or 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 11:30 p.m.