Triple
T8317967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Rome |
E194752
|
entity |
| Predicate | partiallyPreservedThrough |
P81907
|
FINISHED |
| Object | later summaries |
—
|
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: later summaries | Statement: [History of Rome, partiallyPreservedThrough, later summaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyPreservedThrough Context triple: [History of Rome, partiallyPreservedThrough, later summaries]
-
A.
partiallyPreserved
Indicates that the referenced entity or object is only incompletely intact, with some parts missing, damaged, or lost while others remain.
-
B.
partiallyRestored
Indicates that an entity has been brought back toward a previous or original state, but the restoration is incomplete or only partially achieved.
-
C.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
-
D.
restoredInPart
Indicates that something has been brought back to a previous or improved state, but only partially rather than fully.
-
E.
partiallyReusable
Indicates that an entity can be reused to some extent but not fully or indefinitely, implying limited or partial reusability.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f630ea881909fb639383e60aee9 |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 5:55 p.m.