Triple
T28877238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erinna |
E732304
|
entity |
| Predicate | hasWorkPreservedAs |
P21692
|
FINISHED |
| Object | 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: fragments | Statement: [Erinna, hasWorkPreservedAs, fragments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkPreservedAs Context triple: [Erinna, hasWorkPreservedAs, fragments]
-
A.
hasPreserved
Indicates that one entity has kept another entity intact, unchanged, or maintained in its original or functional state over time.
-
B.
workPreservedIn
chosen
Indicates that a work is maintained, stored, or archived within a particular medium, collection, or repository so that it remains accessible over time.
-
C.
isPreservedBy
Indicates that something remains unchanged, intact, or maintained as it is due to the action or influence of a particular agent or process.
-
D.
hasWorkBasedOn
Indicates that one work is derived from, adapted from, or otherwise based on the content of another work.
-
E.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 28, 2026, 7:39 a.m.