Triple
T19418464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1976 Canada Cup |
E485781
|
entity |
| Predicate | bestOnBest |
P135804
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1976 Canada Cup, bestOnBest, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestOnBest Context triple: [1976 Canada Cup, bestOnBest, true]
-
A.
bestOf
Indicates that one entity is the top-ranked or most outstanding member within a specified group, set, or collection.
-
B.
bestCrossed
Indicates that one entity has surpassed or exceeded another in a crossing-related context, such as achieving the most successful or optimal crossing among alternatives.
-
C.
bestKnownSingle
Indicates that the referenced item is the most prominent or widely recognized single associated with an entity (such as an artist or group).
-
D.
holdsBestFor
Indicates that one entity considers or maintains another entity as the most suitable or optimal choice for a particular purpose or context.
-
E.
bestForward
Indicates that the subject is considered the most effective or outstanding forward (e.g., in an offensive or attacking role) relative to a given group or context.
- F. None of above. chosen
Provenance (4 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62afbaf0c8190913eda4b04efbe67 |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.