Triple
T16483174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triple Gold Club membership |
E400372
|
entity |
| Predicate | requiresTitle |
P122950
|
FINISHED |
| Object | Stanley Cup champion |
—
|
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: Stanley Cup champion | Statement: [Triple Gold Club membership, requiresTitle, Stanley Cup champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresTitle Context triple: [Triple Gold Club membership, requiresTitle, Stanley Cup champion]
-
A.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
B.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
C.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
D.
hasTitleSubject
Indicates that an entity has a specific subject or topic as the focus of its title.
-
E.
hasTitleFeature
Indicates that an entity possesses a specific characteristic, attribute, or element related to its title.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e0420ac81908f9a3548ddb3b1ff |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:13 a.m.