Triple
T2649478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archytas |
E53861
|
entity |
| Predicate | reputedRescued |
P24359
|
FINISHED |
| Object | Plato from Dionysius II of Syracuse |
—
|
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: Plato from Dionysius II of Syracuse | Statement: [Archytas, reputedRescued, Plato from Dionysius II of Syracuse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reputedRescued Context triple: [Archytas, reputedRescued, Plato from Dionysius II of Syracuse]
-
A.
allegedRescueEvent
Indicates that an event is claimed or reported to be a rescue, but its occurrence or nature is not confirmed as factual.
-
B.
rescuedBy
Indicates that one entity has been saved or brought out of danger by another entity.
-
C.
rescuedLocation
Indicates the place where a rescue action occurred or from which someone or something was rescued.
-
D.
recoveredIn
Indicates that something lost, damaged, or impaired has been restored or regained within a particular context, process, or location.
-
E.
helpedEscape
chosen
Indicates that one entity assisted another in getting away from confinement, danger, or pursuit.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd91ca1288190ba302b04bac4c153 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.