Triple
T9778848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zosimus |
E237313
|
entity |
| Predicate | survivingWorkCount |
P75578
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Zosimus, survivingWorkCount, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingWorkCount Context triple: [Zosimus, survivingWorkCount, 1]
-
A.
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.
-
B.
extentOfSurvivalOfWork
chosen
Indicates the degree to which a work has been preserved or remains extant.
-
C.
survivorCount
Indicates the number of entities that remain alive or intact after a specified event, process, or condition.
-
D.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
E.
survivesIn
Indicates that an entity remains alive, functional, or intact within a specified environment, condition, or context.
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda13663f081909b95563038eb6485 |
completed | April 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:27 p.m.