Triple
T25005910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Door |
E625839
|
entity |
| Predicate | notablePowerType |
P179176
|
FINISHED |
| Object | portal creation magic |
—
|
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: portal creation magic | Statement: [Door, notablePowerType, portal creation magic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePowerType Context triple: [Door, notablePowerType, portal creation magic]
-
A.
notablePower
Indicates that an entity possesses a significant or distinguished form of power, influence, or capability that is recognized as noteworthy.
-
B.
notableAbsorbedPowersFrom
Indicates that one entity is known for having taken in or acquired powers or abilities from another entity.
-
C.
usesPowerType
Indicates that one entity operates or functions by means of a specified type or source of power.
-
D.
hasHeroPower
Indicates that one entity possesses or is endowed with a special ability or power characteristic of a hero in relation to another entity.
-
E.
notableFeat
Indicates that an entity is recognized for having achieved or performed a particularly significant or distinguished feat.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 18, 2026, 6:05 a.m.