Triple
T37461687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Call of the Wild |
E930932
|
entity |
| Predicate | cardIdContext |
P187878
|
FINISHED |
| Object | Associated with Animal Companion spell |
—
|
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: Associated with Animal Companion spell | Statement: [Call of the Wild, cardIdContext, Associated with Animal Companion spell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardIdContext Context triple: [Call of the Wild, cardIdContext, Associated with Animal Companion spell]
-
A.
cardId
chosen
Indicates a relationship where an entity is associated with a specific card through its unique identifier.
-
B.
cardTypeAccess
Indicates that access or permissions are determined or constrained based on the type of card involved.
-
C.
cardIdPrefix
Indicates that one entity is a prefix of the identifier (ID) of a card associated with the other entity.
-
D.
cardFunction
Indicates that one entity serves as the functional role, capability, or purpose associated with a card-related entity in a system.
-
E.
cardType
Indicates the classification or category assigned to a card within a given system or context.
- 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_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.