Triple
T21045510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1984 Canada Cup |
E518436
|
entity |
| Predicate | roundRobinFormat |
P69430
|
FINISHED |
| Object | single round-robin |
—
|
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: single round-robin | Statement: [1984 Canada Cup, roundRobinFormat, single round-robin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roundRobinFormat Context triple: [1984 Canada Cup, roundRobinFormat, single round-robin]
-
A.
roundFormat
chosen
Indicates the specific structure, rules, or style in which a particular round of an event, game, or process is conducted.
-
B.
roundOf
Indicates that one event, match, or game occurs as a specific stage or phase within a larger competition or tournament.
-
C.
roundel
Indicates that one entity bears, displays, or is marked with a circular emblem or symbol representing another entity.
-
D.
rotatesAmong
Indicates that an entity takes turns occupying or performing a role, position, or function in sequence with other entities.
-
E.
formsLoopAround
Indicates that one entity extends or curves so as to create a closed loop encircling or surrounding another entity or region.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcf3cac081909915a440fbb5c084 |
completed | April 21, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:32 p.m.