Triple
T33049669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghost of Darius I |
E845688
|
entity |
| Predicate | relatedToHistoricalFigure |
P26467
|
FINISHED |
| Object | Darius I of Persia |
E48135
|
NE 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: Darius I of Persia | Statement: [Ghost of Darius I, relatedToHistoricalFigure, Darius I of Persia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToHistoricalFigure Context triple: [Ghost of Darius I, relatedToHistoricalFigure, Darius I of Persia]
-
A.
historicalFigureAssociated
chosen
Indicates that there is a notable connection or linkage between an entity and a historical figure, such as influence, collaboration, representation, or involvement in the figure’s life or legacy.
-
B.
addressesHistoricalFigure
Indicates that one entity directly speaks or writes to a person recognized as a historical figure.
-
C.
basedOnHistoricalFigure
Indicates that something is derived from, inspired by, or modeled after a real historical person.
-
D.
involvesHistoricalFigures
Indicates that the subject is associated with or includes participation by notable individuals from history.
-
E.
historicalFigureDiscussed
Indicates that a historical figure is the topic of discussion, analysis, or commentary in some context.
- F. None of above.
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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3543011fbc81909b50ec6a32b949c5 |
completed | June 19, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:24 a.m.