Triple
T29900096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradox Engine |
E759385
|
entity |
| Predicate | untaps |
P168229
|
FINISHED |
| Object | all nonland permanents you control |
—
|
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: all nonland permanents you control | Statement: [Paradox Engine, untaps, all nonland permanents you control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: untaps Context triple: [Paradox Engine, untaps, all nonland permanents you control]
-
A.
upends
Indicates overturning or disrupting an existing state, order, or expectation, often reversing or radically altering how things were previously arranged or understood.
-
B.
undertecknatAv
Indicates that something (typically a document or agreement) has been signed by a particular party.
-
C.
returnedFromExile
Indicates that an entity has come back to its original place or community after a period of being exiled.
-
D.
أُلغي
Indicates that an action, event, or arrangement has been canceled or annulled.
-
E.
releaseFrom
Indicates that one entity causes or authorizes another entity to be freed, discharged, or removed from a prior state of confinement, obligation, or restriction.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6772e14d48190a9c4dda3d35d0f37 |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:06 p.m.