Triple
T28897905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortus |
E732877
|
entity |
| Predicate | powerOrAbility |
P42064
|
FINISHED |
| Object | brings drawings to life |
—
|
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: brings drawings to life | Statement: [Mortus, powerOrAbility, brings drawings to life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerOrAbility Context triple: [Mortus, powerOrAbility, brings drawings to life]
-
A.
notablePower
Indicates that an entity possesses a significant or distinguished form of power, influence, or capability that is recognized as noteworthy.
-
B.
usesPowerType
Indicates that one entity operates or functions by means of a specified type or source of power.
-
C.
hasSuperpower
chosen
Indicates that one entity possesses a special or extraordinary power or ability beyond normal human capabilities.
-
D.
heroPower
Indicates that an entity possesses or is associated with a particular heroic power or special ability.
-
E.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 28, 2026, 8 a.m.