Triple
T29726289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campbell Bowl |
E752186
|
entity |
| Predicate | finalistsCompeteIn |
P11194
|
FINISHED |
| Object | Western Conference 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: Western Conference Finals | Statement: [Campbell Bowl, finalistsCompeteIn, Western Conference Finals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalistsCompeteIn Context triple: [Campbell Bowl, finalistsCompeteIn, Western Conference Finals]
-
A.
finalists
chosen
Indicates that the related entities have advanced to the final round or stage of a competition, selection process, or evaluation.
-
B.
hasNumberOfFinalists
Indicates the relationship between an entity and the count of finalists associated with it.
-
C.
isFinalsOf
Indicates that one entity represents the final or concluding stage, round, or version of another entity.
-
D.
representsFinals
Indicates that one entity serves as the final or culminating stage, outcome, or version of another entity.
-
E.
finalCompetitiveMatch
Indicates that a given match is the last or concluding competitive contest for the involved participant(s) or team(s).
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 28, 2026, 7:39 p.m.