Triple
T37592193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frostwyrm Lair |
E935286
|
entity |
| Predicate | hasCardUnlock |
P201797
|
FINISHED |
| Object | legendary cards |
—
|
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: legendary cards | Statement: [Frostwyrm Lair, hasCardUnlock, legendary cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCardUnlock Context triple: [Frostwyrm Lair, hasCardUnlock, legendary cards]
-
A.
hasBasicCardSet
Indicates that an entity is associated with or includes a fundamental or default set of cards.
-
B.
usesCard
Indicates that an entity employs or relies on a specific card (e.g., payment, access, or identification card) to perform an action or participate in an interaction.
-
C.
hasUnlockableStatusInSomeRegions
Indicates that the subject is restricted or locked in certain regions but can be made available or unlocked there under specific conditions.
-
D.
hasCardinal
Indicates that something possesses or is associated with a specific cardinal number or quantity.
-
E.
hasNotableCardFamily
Indicates that an entity is associated with a specific, distinguished group or family of related cards.
- F. None of above. chosen
Provenance (4 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a002249ee388190a9501ee7630dc658 |
completed | May 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_6a002189273881909b6b687e2d61f5b1 |
completed | May 10, 2026, 6:11 a.m. |
| PDg | Predicate description generation | batch_6a0022494be881908bdf945d2393a40f |
completed | May 10, 2026, 6:14 a.m. |
Created at: May 3, 2026, 4:18 p.m.