Triple
T37462575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyrantus |
E930954
|
entity |
| Predicate | hasFormatLegality |
P188675
|
FINISHED |
| Object | Wild |
—
|
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: Wild | Statement: [Tyrantus, hasFormatLegality, Wild]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormatLegality Context triple: [Tyrantus, hasFormatLegality, Wild]
-
A.
formatLegality
Indicates whether a particular item, action, or configuration complies with or violates a specified set of rules, standards, or laws.
-
B.
cardFormatLegality
chosen
Indicates whether a particular card is legally playable within a specified game format or ruleset.
-
C.
formatLegalityAtRelease
Indicates whether a particular format was legally permitted or compliant at the time of its initial release.
-
D.
meetsFormat
Indicates that something conforms to, satisfies, or is compliant with a specified format or structural standard.
-
E.
hasFormatSpecification
Indicates that something is associated with a particular format definition or specification that describes how it should be structured or represented.
- 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_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 3, 2026, 4:17 p.m.