Triple
T29900136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradox Engine |
E759385
|
entity |
| Predicate | isLegendary |
P122560
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Paradox Engine, isLegendary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLegendary Context triple: [Paradox Engine, isLegendary, true]
-
A.
isLegendaryStatus
chosen
Indicates that an entity possesses a legendary status, typically signifying exceptional rarity, renown, or significance within a given context.
-
B.
hasLegendaryPokémon
Indicates that an entity (such as a location, trainer, or group) possesses, contains, or is associated with at least one Legendary Pokémon.
-
C.
isMythical
Indicates that the entity is considered mythical, existing only in legend, folklore, or imagination rather than in reality.
-
D.
hasLegendaryPlayer
Indicates that an entity (such as a team, club, or organization) is associated with at least one player recognized as legendary.
-
E.
includesLegendaryCard
Indicates that an entity (such as a deck, pack, or collection) contains at least one legendary card.
- 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_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_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:06 p.m.