Triple
T37463583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rin, the First Disciple |
E930978
|
entity |
| Predicate | deckStrategy |
P187926
|
FINISHED |
| Object | Control Warlock |
—
|
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: Control Warlock | Statement: [Rin, the First Disciple, deckStrategy, Control Warlock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deckStrategy Context triple: [Rin, the First Disciple, deckStrategy, Control Warlock]
-
A.
deckStrength
Indicates the relative power or effectiveness of a deck in a game or competitive setting.
-
B.
cardGameMode
Indicates the specific mode or rule set under which a card game is being played or configured.
-
C.
opponentStrategy
Indicates that one entity employs or represents a strategic plan specifically designed to counter or compete against another entity.
-
D.
deckLocation
Indicates the specific deck or level on which an entity is located within a multi-deck structure or vehicle.
-
E.
deckArchetype
chosen
Indicates a classification relationship where a specific deck is associated with a particular strategic archetype or style of play.
- 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_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.