Triple
T19832343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mares of Diomedes |
E476493
|
entity |
| Predicate | fateInSomeVersions |
P115742
|
FINISHED |
| Object | released and eaten by wild beasts |
—
|
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: released and eaten by wild beasts | Statement: [Mares of Diomedes, fateInSomeVersions, released and eaten by wild beasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateInSomeVersions Context triple: [Mares of Diomedes, fateInSomeVersions, released and eaten by wild beasts]
-
A.
fateInSequel
Indicates that the outcome or destiny of an entity is revealed or occurs in a subsequent work, installment, or sequel.
-
B.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
C.
fateInLegend
chosen
Indicates the ultimate outcome or destiny attributed to an entity within a particular legend or mythic narrative.
-
D.
fateInBooks
Indicates that a character’s destiny, outcome, or predetermined path is described or revealed within written works or books.
-
E.
fateLocation
Indicates the location where an entity ultimately ends up or meets its final outcome.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656cf7e488190b4be28b5e7b363bf |
completed | April 20, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.