Triple
T37464720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragonqueen Alexstrasza |
E931004
|
entity |
| Predicate | generatedCardsSourcePool |
P189037
|
FINISHED |
| Object | other collectible Dragons |
—
|
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: other collectible Dragons | Statement: [Dragonqueen Alexstrasza, generatedCardsSourcePool, other collectible Dragons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generatedCardsSourcePool Context triple: [Dragonqueen Alexstrasza, generatedCardsSourcePool, other collectible Dragons]
-
A.
cardSet
Indicates that an item belongs to, or is grouped within, a particular set or collection of cards.
-
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.
hasNumberOfCards
Indicates that an entity is associated with a specific quantity of cards.
-
D.
generatesCard
chosen
Indicates that one entity creates or produces a card for another entity or for some purpose.
-
E.
uniquePerDeck
Indicates that each deck can contain at most one instance of the related item or element.
- 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_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:17 p.m.