Triple
T11272589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purifications |
E266849
|
entity |
| Predicate | fragmentStatus |
P98867
|
FINISHED |
| Object | survives only in fragments |
—
|
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: survives only in fragments | Statement: [Purifications, fragmentStatus, survives only in fragments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fragmentStatus Context triple: [Purifications, fragmentStatus, survives only in fragments]
-
A.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
compositionStatus
Indicates the current state or phase of completion of a composition or creative work, such as whether it is planned, in progress, revised, or finalized.
-
C.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
D.
draftStatus
Indicates the current stage or condition of an item within a drafting or revision process (e.g., whether it is in draft, under review, or finalized).
-
E.
materialStatus
Indicates the current state or condition of a material, such as its availability, usage, or processing stage.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e965c9048190804ebb48f0a4817b |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
| PDg | Predicate description generation | batch_69d796cf74308190a5b29d0dd82954a2 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:31 p.m.