Triple
T3306881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horatii brothers |
E69471
|
entity |
| Predicate | relatedLegend |
P1582
|
FINISHED |
| Object | story of Horatius who killed his sister |
—
|
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: story of Horatius who killed his sister | Statement: [Horatii brothers, relatedLegend, story of Horatius who killed his sister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedLegend Context triple: [Horatii brothers, relatedLegend, story of Horatius who killed his sister]
-
A.
legend
Indicates that an entity is a traditional or historical story, figure, or narrative widely regarded as legendary rather than strictly factual.
-
B.
hasLegendAssociatedWith
chosen
Indicates that something is connected to or accompanied by a traditional story, myth, or legend.
-
C.
legendLocation
Indicates the place or setting where a particular legend, myth, or traditional story is situated or associated.
-
D.
linkedFigure
Indicates that one figure is associated or connected to another figure, typically as a reference or related visual element.
-
E.
relatedCurve
Indicates that one curve is associated with or derived from another curve in a defined relational way.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0caa0988190872fc7648e64571f |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.