Triple
T29726287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campbell Bowl |
E752186
|
entity |
| Predicate | relatedTrophyRole |
P28247
|
FINISHED |
| Object | Eastern Conference playoff champion trophy |
—
|
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: Eastern Conference playoff champion trophy | Statement: [Campbell Bowl, relatedTrophyRole, Eastern Conference playoff champion trophy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedTrophyRole Context triple: [Campbell Bowl, relatedTrophyRole, Eastern Conference playoff champion trophy]
-
A.
hasRelatedTrophy
chosen
Indicates that there exists a trophy that is associated with, linked to, or relevant to the given entity.
-
B.
relationshipToPlayer
Indicates the type of personal or social connection an entity has with the player.
-
C.
relatedMedal
Indicates a relationship where one entity is associated with, corresponds to, or is linked to a particular medal (such as an award, honor, or decoration).
-
D.
trophySharedBy
Indicates that a particular trophy is jointly possessed, held, or credited to multiple entities.
-
E.
associatedAchievement
Indicates a relationship where one entity is linked to, or recognized in connection with, a particular achievement.
- 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_6a01a48fbbd481908ccf75551dcf4647 |
completed | May 11, 2026, 9:42 a.m. |
| PD | Predicate disambiguation | batch_6a01a2d6db208190b11c1af601a544f5 |
completed | May 11, 2026, 9:35 a.m. |
Created at: April 28, 2026, 7:39 p.m.