Triple
T9707314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demiurge |
E234931
|
entity |
| Predicate | reinterpretedIn |
P20254
|
FINISHED |
| Object | Gnostic systems |
—
|
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: Gnostic systems | Statement: [Demiurge, reinterpretedIn, Gnostic systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reinterpretedIn Context triple: [Demiurge, reinterpretedIn, Gnostic systems]
-
A.
laterReinterpretedAs
Indicates that something was originally understood or classified one way but was subsequently given a different interpretation or meaning at a later time.
-
B.
interpretedFor
Indicates that one entity has been interpreted, translated, or explained on behalf of or for the benefit of another entity.
-
C.
reconstructedIn
Indicates that something has been rebuilt, restored, or re-created within a particular context, location, or medium.
-
D.
interpretedInCase
Indicates that something is understood, analyzed, or given meaning within the context of a particular case or specific situational scenario.
-
E.
isInterpretedDifferentlyIn
chosen
Indicates that the same item, event, or expression is understood or construed in a different way within a specified context, group, or setting.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9da4c53c81908ba4bfe4d9ca8814 |
completed | April 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:19 p.m.