Triple
T37464353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overkill |
E930996
|
entity |
| Predicate | belongsToClassCards |
P99617
|
FINISHED |
| Object | Warrior |
—
|
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: Warrior | Statement: [Overkill, belongsToClassCards, Warrior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToClassCards Context triple: [Overkill, belongsToClassCards, Warrior]
-
A.
hasClassSpecificCards
Indicates that certain cards are restricted to, or specifically associated with, a particular class or category.
-
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.
cardClass
chosen
Indicates the classification or category to which a given card belongs within a defined card system or schema.
-
D.
containsCard
Indicates that one entity includes or holds a specific card as part of its contents or collection.
-
E.
cardSet
Indicates that an item belongs to, or is grouped within, a particular set or collection of cards.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a002103c93081908398fa5726f5fa6e |
completed | May 10, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_6a001fcb9fb48190a27d8f2ca983fbe6 |
completed | May 10, 2026, 6:03 a.m. |
Created at: May 3, 2026, 4:17 p.m.