Triple
T36731936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telamonian Ajax |
E907363
|
entity |
| Predicate | rescuedBodyOf |
P98142
|
FINISHED |
| Object | Patroclus |
—
|
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: Patroclus | Statement: [Telamonian Ajax, rescuedBodyOf, Patroclus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rescuedBodyOf Context triple: [Telamonian Ajax, rescuedBodyOf, Patroclus]
-
A.
rescuesBodyOf
chosen
Indicates that one entity retrieves and brings to safety the body of another entity from a dangerous or inaccessible situation.
-
B.
rescuedInFormOf
Indicates that one entity is rescued, saved, or recovered specifically in the form, state, or manifestation represented by another entity.
-
C.
rescuedTo
Indicates that one entity has been saved or freed from danger, harm, or a problematic situation and brought to the safety or custody of another entity or location.
-
D.
bodiesRecovered
Indicates that the remains of deceased individuals have been found and retrieved from a location or incident.
-
E.
rescuedDuring
Indicates that one entity was rescued in the course of, or as part of, a specified event or time period.
- 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.