Triple
T38263273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WHA 1978–79 season |
E1017983
|
entity |
| Predicate | hasFinalsName |
P115592
|
FINISHED |
| Object | Avco World Trophy Finals |
—
|
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: Avco World Trophy Finals | Statement: [WHA 1978–79 season, hasFinalsName, Avco World Trophy Finals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinalsName Context triple: [WHA 1978–79 season, hasFinalsName, Avco World Trophy Finals]
-
A.
isFinalsOf
Indicates that one entity represents the final or concluding stage, round, or version of another entity.
-
B.
hasFinalsSeries
chosen
Indicates that there exists a specific finals series associated with or assigned to a given entity.
-
C.
hasFinalRound
Indicates that an event, process, or competition includes a concluding or decisive final round.
-
D.
hasFinalMatch
Indicates that an entity is associated with a concluding or decisive match in a series, tournament, or competition.
-
E.
hasFinalTournament
Indicates that an entity is associated with a specific tournament that serves as its final or concluding 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0082989e6c819099fea0e706332e37 |
completed | May 10, 2026, 1:05 p.m. |
| PD | Predicate disambiguation | batch_6a0081ed6a1481908baf472876e28db9 |
completed | May 10, 2026, 1:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.