Triple
T19242425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sychaeus |
E481164
|
entity |
| Predicate | revealsInDream |
P102755
|
FINISHED |
| Object | his murder by Pygmalion |
—
|
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: his murder by Pygmalion | Statement: [Sychaeus, revealsInDream, his murder by Pygmalion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revealsInDream Context triple: [Sychaeus, revealsInDream, his murder by Pygmalion]
-
A.
interpretedDreamFor
Indicates that one entity has provided an explanation or analysis of the meaning of another entity’s dream.
-
B.
dreamsSignified
Indicates that one entity’s dreams symbolically represent, foreshadow, or convey information about another entity or situation.
-
C.
dream
Indicates that an entity experiences or has a dream involving another entity or concept.
-
D.
typeOfRevelation
Indicates the specific manner or category of revelation through which information, truth, or insight is disclosed.
-
E.
dreamProjectionForm
chosen
Indicates a relationship where one entity appears or manifests in a particular form within another entity’s dream or dreamlike projection.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faf2353c819094a9a1af3a858715 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:27 p.m.