Triple
T37464468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twinspell |
E930999
|
entity |
| Predicate | copyRetainsCardText |
P188368
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Twinspell, copyRetainsCardText, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: copyRetainsCardText Context triple: [Twinspell, copyRetainsCardText, true]
-
A.
cardText
Indicates that one entity is the textual content displayed on a card associated with another entity.
-
B.
legalCardsFrom
Indicates that the referenced cards are permitted or valid according to the rules or constraints defined by the specified source or authority.
-
C.
usesMinimumCopiesPerCard
Indicates that there is a constraint specifying the minimum number of copies of each card that must be used or included in a given context.
-
D.
containsCard
Indicates that one entity includes or holds a specific card as part of its contents or collection.
-
E.
iconicTCGCard
Indicates that a trading card game (TCG) card is widely recognized as emblematic or highly representative of its game or format.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba67f78348190ab160988e4698394 |
completed | May 6, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.