Triple
T26398095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans-Tasman football rivalry |
E663625
|
entity |
| Predicate | broaderRivalryContext |
P16079
|
FINISHED |
| Object | Trans-Tasman sporting rivalry |
—
|
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: Trans-Tasman sporting rivalry | Statement: [Trans-Tasman football rivalry, broaderRivalryContext, Trans-Tasman sporting rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broaderRivalryContext Context triple: [Trans-Tasman football rivalry, broaderRivalryContext, Trans-Tasman sporting rivalry]
-
A.
involvesRivalryBetween
Indicates a relationship in which two or more entities are engaged in rivalry or competitive opposition with one another.
-
B.
rivalryImpact
Indicates how a rivalry between entities influences their behaviors, outcomes, or interactions.
-
C.
competitiveContext
chosen
Indicates a situation in which entities are engaged in or influenced by competition with one another.
-
D.
typeOfRivalry
Indicates a competitive or adversarial relationship between entities, specifying the particular kind or nature of rivalry that exists between them.
-
E.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
- 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_69f610f1f6508190a1540b6a7d3568f9 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 11:30 p.m.