Triple
T9311344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ammianus Marcellinus |
E224012
|
entity |
| Predicate | workSurvivingCoverage |
P75578
|
FINISHED |
| Object | 353–378 |
—
|
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: 353–378 | Statement: [Ammianus Marcellinus, workSurvivingCoverage, 353–378]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workSurvivingCoverage Context triple: [Ammianus Marcellinus, workSurvivingCoverage, 353–378]
-
A.
workCovered
Indicates that one work or effort is included within the scope, protection, or responsibility defined by another entity or arrangement.
-
B.
survivingWorkForm
Indicates that one work is a surviving or extant form/version of another, typically when the original or earlier form is lost or no longer available.
-
C.
extentOfSurvivalOfWork
chosen
Indicates the degree to which a work has been preserved or remains extant.
-
D.
medicalCoverageAfter
Indicates that one entity’s medical insurance coverage begins or applies after the time, event, or coverage period associated with another entity.
-
E.
primaryCoverage
Indicates that one entity serves as the main or principal source of coverage (such as insurance or protection) for 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20ad3b20819092562c30e70a528f |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.