Triple
T37554805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frenzy |
E933669
|
entity |
| Predicate | hasCardTextPattern |
P197650
|
FINISHED |
| Object | Frenzy: [effect text] |
—
|
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: Frenzy: [effect text] | Statement: [Frenzy, hasCardTextPattern, Frenzy: [effect text]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCardTextPattern Context triple: [Frenzy, hasCardTextPattern, Frenzy: [effect text]]
-
A.
hasTextIn
chosen
Indicates that an entity contains or is associated with a specific piece of text within a particular context or location.
-
B.
containsCard
Indicates that one entity includes or holds a specific card as part of its contents or collection.
-
C.
containsText
Indicates that one entity includes the specified text string within its content.
-
D.
hasClassSpecificCards
Indicates that certain cards are restricted to, or specifically associated with, a particular class or category.
-
E.
hasMatchCardType
Indicates that two or more items share the same card type or that an item is associated with a specific matching card type.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a001adc8c108190ab3a43f6415e2be3 |
completed | May 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a001a290330819097c2c3123f9014b4 |
completed | May 10, 2026, 5:39 a.m. |
Created at: May 3, 2026, 4:17 p.m.