Triple
T14775327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curiatii brothers |
E347243
|
entity |
| Predicate | fateInLegend |
P115742
|
FINISHED |
| Object | killed in duel with Horatii |
—
|
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: killed in duel with Horatii | Statement: [Curiatii brothers, fateInLegend, killed in duel with Horatii]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateInLegend Context triple: [Curiatii brothers, fateInLegend, killed in duel with Horatii]
-
A.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
B.
fateInBooks
Indicates that a character’s destiny, outcome, or predetermined path is described or revealed within written works or books.
-
C.
knowledgeOfFate
Indicates that one entity is aware of or understands the destined or predetermined outcome concerning another entity or event.
-
D.
fateLocation
Indicates the location where an entity ultimately ends up or meets its final outcome.
-
E.
guidesFateOf
Indicates a relationship where one entity directs, shapes, or determines the destiny or ultimate outcome of another entity.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec815dd5081909e927911c06b2d66 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:31 a.m.