Triple
T37458150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgl the Oracle |
E930849
|
entity |
| Predicate | cardSetStatus |
P188662
|
FINISHED |
| Object | evergreen |
—
|
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: evergreen | Statement: [Morgl the Oracle, cardSetStatus, evergreen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardSetStatus Context triple: [Morgl the Oracle, cardSetStatus, evergreen]
-
A.
cardSet
Indicates that an item belongs to, or is grouped within, a particular set or collection of cards.
-
B.
cardNumberInSet
Indicates that a specific card has a particular number or position within a defined set or collection of cards.
-
C.
cardSetType
Indicates the classification relationship that specifies what type or category a given card set belongs to.
-
D.
cardId
Indicates a relationship where an entity is associated with a specific card through its unique identifier.
-
E.
T206CardStatus
Indicates the current operational or validity state assigned to a card (such as active, inactive, blocked, or expired) within a system or process.
- 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_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. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.