Triple
T34046394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phanes |
E873097
|
entity |
| Predicate | gaveScepterTo |
P58020
|
FINISHED |
| Object | Nyx |
—
|
NE NERFINISHED |
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: Nyx | Statement: [Phanes, gaveScepterTo, Nyx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gaveScepterTo Context triple: [Phanes, gaveScepterTo, Nyx]
-
A.
offeredCrownTo
chosen
Indicates that one entity formally presented or proposed a royal crown or rulership to another entity.
-
B.
hasArmsGrantedBy
Indicates that one entity has been formally granted heraldic arms or a coat of arms by another entity (such as a monarch, heraldic authority, or institution).
-
C.
grantedBoonTo
Indicates that one entity has bestowed a favor, benefit, or special privilege upon another entity.
-
D.
handedDownBy
Indicates that something (such as an object, tradition, or decision) is transferred or passed from one entity to another, typically from an earlier holder or authority to a later recipient.
-
E.
Seal of the Hands
Indicates a relationship in which something is formally confirmed, authenticated, or bound through the deliberate action or agreement of specific individuals or parties.
- 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_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.