Triple
T20778390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cepheus |
E511413
|
entity |
| Predicate | rescuedByProxy |
P141491
|
FINISHED |
| Object | Perseus saved Andromeda |
—
|
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: Perseus saved Andromeda | Statement: [Cepheus, rescuedByProxy, Perseus saved Andromeda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rescuedByProxy Context triple: [Cepheus, rescuedByProxy, Perseus saved Andromeda]
-
A.
rescuedBy
Indicates that one entity has been saved or brought out of danger by another entity.
-
B.
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.
-
C.
rescuedInFormOf
Indicates that one entity is rescued, saved, or recovered specifically in the form, state, or manifestation represented by another entity.
-
D.
rescuedDuring
Indicates that one entity was rescued in the course of, or as part of, a specified event or time period.
-
E.
rescuesWith
Indicates that one entity saves or frees another entity from danger, harm, or captivity using a particular means, tool, or method.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c26d34bc81908bb22087d434322d |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:37 p.m.