Triple
T26398124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans-Tasman football rivalry |
E663625
|
entity |
| Predicate | continentContextTeam1 |
P55885
|
FINISHED |
| Object | Australia |
—
|
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: Australia | Statement: [Trans-Tasman football rivalry, continentContextTeam1, Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentContextTeam1 Context triple: [Trans-Tasman football rivalry, continentContextTeam1, Australia]
-
A.
continentTeam1
chosen
Indicates that the first team is associated with or belongs to a particular continent.
-
B.
continentTeam2
Indicates that the second team is associated with or belongs to a particular continent.
-
C.
stateTeam1
Indicates that the first team is associated with, represents, or belongs to a particular state.
-
D.
locationTeam1Home
Indicates that the specified location serves as the home venue or home ground for team 1 in the relationship.
-
E.
locationTeam1City
Indicates the city where the first team involved in the relationship is located.
- 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_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 26, 2026, 11:30 p.m.