Triple
T19083681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polydorus |
E467089
|
entity |
| Predicate | bodyDisposed |
P35082
|
FINISHED |
| Object | thrown into the sea |
—
|
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: thrown into the sea | Statement: [Polydorus, bodyDisposed, thrown into the sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyDisposed Context triple: [Polydorus, bodyDisposed, thrown into the sea]
-
A.
bodyDisposedIn
chosen
Indicates that a body (typically a dead organism or corpse) is placed, discarded, or otherwise disposed of within a particular location or container.
-
B.
bodyDisposedBy
Indicates that a body is disposed of, handled, or gotten rid of by a particular agent or entity.
-
C.
bodyFinish
Indicates that one entity completes or finishes the main body or primary portion of another entity.
-
D.
losesBodyPart
Indicates that an entity has a body part removed, detached, or otherwise ceases to possess a specific body part.
-
E.
bodyFound
Indicates that the location or circumstance where a body was discovered has been identified or recorded.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e34600f88190bd96bcc2c5c08d14 |
completed | April 20, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.