Triple
T1014696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dione |
E21903
|
entity |
| Predicate | associatedFunction |
P23285
|
FINISHED |
| Object | prophecy |
—
|
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: prophecy | Statement: [Dione, associatedFunction, prophecy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedFunction Context triple: [Dione, associatedFunction, prophecy]
-
A.
assignedFunction
Indicates that a specific role, duty, or function has been formally allocated to an entity.
-
B.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
C.
associatedOperation
Indicates that one entity is linked to or involved with a particular operation, process, or activity.
-
D.
possibleFunction
Indicates that an entity may serve, or is capable of serving, a particular function or role, without asserting that it actually does so.
-
E.
associatedCommand
Indicates a relationship where one entity is linked to, or meant to be used with, a particular command or set of commands.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c05060819083c51717874074c8 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b72207c08190a3dbb2aa7acbbc71 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7bd3d50819091e6f1d2ffe4c7ee |
completed | March 1, 2026, 10:03 p.m. |
Created at: March 1, 2026, 7:41 p.m.