Triple
T18695024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ἀγαμέμνων |
E457093
|
entity |
| Predicate | killedAfterEvent |
P132319
|
FINISHED |
| Object | return from Troy |
—
|
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: return from Troy | Statement: [Ἀγαμέμνων, killedAfterEvent, return from Troy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killedAfterEvent Context triple: [Ἀγαμέμνων, killedAfterEvent, return from Troy]
-
A.
killedDuring
Indicates that one entity caused the death of another entity in the course of, or as part of, a specified event or time period.
-
B.
killedAt
Indicates that a killing event occurred at a specific location or time associated with the entities involved.
-
C.
killedBy
Indicates that one entity caused the death of another entity.
-
D.
killedApproximate
Indicates that one entity caused the death of another, but the information about this killing is uncertain, estimated, or not known with exact precision.
-
E.
killedAlongWith
Indicates that one entity was killed at the same time and in the same event or circumstance as 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e66a188190801fd95f9be26042 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:49 a.m.