Triple
T37465301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metamorphosis |
E931018
|
entity |
| Predicate | isLegendarySingletonRule |
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: [Metamorphosis, isLegendarySingletonRule, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLegendarySingletonRule Context triple: [Metamorphosis, isLegendarySingletonRule, true]
-
A.
legendaryRule
Indicates that an entity holds a unique, mythic or legendary status that governs or constrains how it can exist or interact within a given system or context.
-
B.
isLegendaryStatus
chosen
Indicates that an entity possesses a legendary status, typically signifying exceptional rarity, renown, or significance within a given context.
-
C.
isLegendaryMinionForClass
Indicates that a minion is a legendary card specifically associated with a given class.
-
D.
isLegendaryForSet
Indicates that an entity is classified as a legendary item specifically within the context of a given set or collection.
-
E.
versionExclusiveLegendary
Indicates that a legendary entity is available only in a specific version (or set of versions) and not in others.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.