Triple
T4270575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poetics |
E96931
|
entity |
| Predicate | partiallySurvivesAs |
P47939
|
FINISHED |
| Object | treatise on tragedy |
—
|
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: treatise on tragedy | Statement: [Poetics, partiallySurvivesAs, treatise on tragedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallySurvivesAs Context triple: [Poetics, partiallySurvivesAs, treatise on tragedy]
-
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.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
D.
survivingPortions
chosen
Indicates that certain parts or segments of something remain intact or extant after other portions have been lost, destroyed, or removed.
-
E.
partiallyPreserved
Indicates that the referenced entity or object is only incompletely intact, with some parts missing, damaged, or lost while others remain.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ffb85a88190af000b94673bff59 |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347faa45481908c19c29fb906dc92 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.