Triple
T8682898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Private Life of Helen of Troy |
E206080
|
entity |
| Predicate | partiallySurvives |
P35792
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [The Private Life of Helen of Troy, partiallySurvives, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallySurvives Context triple: [The Private Life of Helen of Troy, partiallySurvives, Yes]
-
A.
survivesAs
Indicates that one entity continues to exist or persist in place of, or after the end or transformation of, another entity.
-
B.
survivesIn
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
-
C.
partiallyDestroyed
Indicates that an entity has been damaged or ruined to a significant extent but not completely destroyed.
-
D.
partiallyPreserved
chosen
Indicates that the referenced entity or object is only incompletely intact, with some parts missing, damaged, or lost while others remain.
-
E.
survivingPortions
Indicates that certain parts or segments of something remain intact or extant after other portions have been lost, destroyed, or removed.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae82e508190b0243328e98fcb1d |
completed | March 31, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.