Triple
T31937394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Thoas of Lemnos |
E815427
|
entity |
| Predicate | isSparedBy |
P21179
|
FINISHED |
| Object | Hypsipyle |
—
|
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: Hypsipyle | Statement: [King Thoas of Lemnos, isSparedBy, Hypsipyle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSparedBy Context triple: [King Thoas of Lemnos, isSparedBy, Hypsipyle]
-
A.
laterSparedBy
Indicates that an entity was initially at risk but was subsequently spared or saved by another entity at a later time.
-
B.
sparedPerson
chosen
Indicates that one entity chose not to harm, punish, or otherwise negatively affect another entity when it had the power or opportunity to do so.
-
C.
conditionForSparing
Indicates that one entity specifies the circumstances under which another entity is exempted from harm, penalty, or adverse action.
-
D.
isExpendable
Indicates that the entity can be sacrificed, discarded, or removed without causing unacceptable loss or consequence to the overall system or objective.
-
E.
isOverlookedBy
Indicates that one entity has a view over or looks down upon another entity from a higher or vantage position.
- 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_69f6b26d4b5c8190bde4c96bf1860698 |
completed | May 3, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:05 a.m.