Triple
T2679975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metamorphoses by Apuleius |
E56549
|
entity |
| Predicate | placeInApuleiusCorpus |
P42193
|
FINISHED |
| Object | major work |
—
|
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: major work | Statement: [Metamorphoses by Apuleius, placeInApuleiusCorpus, major work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInApuleiusCorpus Context triple: [Metamorphoses by Apuleius, placeInApuleiusCorpus, major work]
-
A.
positionInAuthorOeuvre
Indicates the relative placement or order of a work within an author's overall body of work.
-
B.
placeInSeries
Indicates the position or order that something occupies within a sequence or series.
-
C.
literaryUnit
Indicates that one entity is a distinct segment or component (such as a chapter, scene, or passage) within a larger literary work or text.
-
D.
isPosthumousWorkOf
Indicates that a work was created, published, or became known only after the death of the person with whom it is associated.
-
E.
setInFictionalLocation
Indicates that an event, story, or narrative takes place within a fictional or imagined location rather than a real-world setting.
- 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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abda2f7bf88190a1e3103dd014d871 |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd81ab9d08190b72b6104c6dbc769 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abda2dc5788190b4b83cb9ed08266c |
completed | March 7, 2026, 7:56 a.m. |
Created at: March 6, 2026, 9:54 p.m.