Triple
T30346997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mephisto Pheles |
E771892
|
entity |
| Predicate | demonKingDomain |
P169408
|
FINISHED |
| Object | Time |
—
|
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: Time | Statement: [Mephisto Pheles, demonKingDomain, Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demonKingDomain Context triple: [Mephisto Pheles, demonKingDomain, Time]
-
A.
kingdomDomain
Indicates that a kingdom is part of, or belongs within, a particular higher-level domain.
-
B.
deityDomain
Indicates that a deity has authority, influence, or primary association over a particular domain, aspect, or sphere of existence.
-
C.
clientKingdomOf
Indicates a relationship where one kingdom is politically subordinate or tributary to another, more powerful kingdom while retaining limited internal autonomy.
-
D.
stateOfDevils
Indicates a condition, status, or situation specifically associated with devils.
-
E.
deathRealm
Indicates a realm, domain, or state specifically associated with death or the dead.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682084db081909e261c5bbae024e3 |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 7:56 p.m.