Triple
T34988713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yu-Gi-Oh! |
E1009323
|
entity |
| Predicate | tradingCardGameType |
P199603
|
FINISHED |
| Object | collectible card game |
—
|
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: collectible card game | Statement: [Yu-Gi-Oh!, tradingCardGameType, collectible card game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradingCardGameType Context triple: [Yu-Gi-Oh!, tradingCardGameType, collectible card game]
-
A.
tradingCardGamePublisher
Indicates that the subject is the publisher responsible for producing or distributing the specified trading card game.
-
B.
cardSetType
Indicates the classification relationship that specifies what type or category a given card set belongs to.
-
C.
iconicTCGCard
Indicates that a trading card game (TCG) card is widely recognized as emblematic or highly representative of its game or format.
-
D.
cardGameAssociatedWith
Indicates that there is a relationship of association between a card game and another entity, such as a person, place, event, or concept.
-
E.
cardGameMode
Indicates the specific mode or rule set under which a card game is being played or configured.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
| PDg | Predicate description generation | batch_69ff4818bb288190b4a27576fad18e23 |
completed | May 9, 2026, 2:43 p.m. |
Created at: May 3, 2026, 4:01 p.m.