Triple
T34046239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phantasos |
E873093
|
entity |
| Predicate | roleInDreams |
P42552
|
FINISHED |
| Object | creates unreal dream images |
—
|
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: creates unreal dream images | Statement: [Phantasos, roleInDreams, creates unreal dream images]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInDreams Context triple: [Phantasos, roleInDreams, creates unreal dream images]
-
A.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
B.
roleInRhyme
Indicates the specific function or part an entity plays within a rhyme, such as a character, object, or structural element of the rhyming text.
-
C.
roleOfCharacter
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
-
D.
roleInStories
chosen
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
E.
roleInTheProphecy
Indicates that an entity holds a specific function, status, or significance within the context of a particular prophecy.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00b6e163308190adeb1d6eb8558641 |
completed | May 10, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_6a00b67e0e388190b08ad66cee4cb0d7 |
completed | May 10, 2026, 4:46 p.m. |
Created at: May 1, 2026, 1:51 a.m.