Triple
T31937591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archemorus |
E815433
|
entity |
| Predicate | deathInterpretedBy |
P101493
|
FINISHED |
| Object | Amphiaraus |
—
|
NE NERFINISHED |
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: Amphiaraus | Statement: [Archemorus, deathInterpretedBy, Amphiaraus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathInterpretedBy Context triple: [Archemorus, deathInterpretedBy, Amphiaraus]
-
A.
deathInterpretedAs
chosen
Indicates that one entity’s death is understood, framed, or interpreted in a particular way by another entity or within a given context.
-
B.
containsDeathOf
Indicates that the subject includes, depicts, or involves the death of the referenced entity.
-
C.
discoveredAsDeadBy
Indicates that one entity was found to be dead by another entity, who discovered their deceased state.
-
D.
diesInAct
Indicates that an entity dies during the course of a specified action or event.
-
E.
deathDescribedBy
Indicates that a death event is documented, characterized, or explained by a specific description or source.
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 12:05 a.m.