Triple
T9421152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moloch |
E227153
|
entity |
| Predicate | laterCharacterizedAs |
P37427
|
FINISHED |
| Object | demon |
—
|
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: demon | Statement: [Moloch, laterCharacterizedAs, demon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterCharacterizedAs Context triple: [Moloch, laterCharacterizedAs, demon]
-
A.
laterDescribedAs
chosen
Indicates that an entity is referred to or characterized by a particular description or label at a later time.
-
B.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
C.
subsequentCharacterization
Indicates that one characterization or description of something occurs later in time than, and in relation to, an earlier characterization of the same thing.
-
D.
languageCharacterizedBy
Indicates that a language is defined or distinguished by a particular feature, property, or characteristic.
-
E.
ruleCharacterization
Indicates that one rule is described, defined, or characterized in terms of another rule or set of rules.
- 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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd6c2528c8819087b0a21e703254b7 |
completed | April 1, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:48 p.m.