Triple
T37788242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sports Champions |
E942013
|
entity |
| Predicate | supportsTrophies |
P60512
|
FINISHED |
| Object | PlayStation Trophies |
E640567
|
NE 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: PlayStation Trophies | Statement: [Sports Champions, supportsTrophies, PlayStation Trophies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTrophies Context triple: [Sports Champions, supportsTrophies, PlayStation Trophies]
-
A.
hasTrophyStatus
Indicates that an entity possesses a particular trophy-related status or classification.
-
B.
trophyCount
Indicates the number of trophies associated with a given entity.
-
C.
hasDomesticTrophies
Indicates that an entity has won or possesses trophies or titles in domestic (national-level) competitions.
-
D.
trophySponsor
Indicates that a sponsor provides financial or material support specifically for a trophy associated with an event, competition, or award.
-
E.
trophyUse
chosen
Indicates that an entity uses, employs, or utilizes a trophy in some manner or context.
- F. None of above.
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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40f181f75c8190aea1e2bab7c7a8ba |
completed | June 28, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.