Triple
T38303580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thoas |
E1032285
|
entity |
| Predicate | sparedFrom |
P21179
|
FINISHED |
| Object | massacre of the men on Lemnos |
—
|
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: massacre of the men on Lemnos | Statement: [Thoas, sparedFrom, massacre of the men on Lemnos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sparedFrom Context triple: [Thoas, sparedFrom, massacre of the men on Lemnos]
-
A.
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.
-
B.
laterSparedBy
Indicates that an entity was initially at risk but was subsequently spared or saved by another entity at a later time.
-
C.
typicallySpared
Indicates that an entity is usually not affected by, excluded from, or left untouched by a particular action, process, or condition.
-
D.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
E.
avoidedFor
Indicates that one entity is deliberately not used, chosen, or engaged with because of the presence, influence, or characteristics of another entity.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.