Triple
T32966895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudens |
E843393
|
entity |
| Predicate | locationInPlautusCorpus |
P204209
|
FINISHED |
| Object | one of Plautus’s later plays |
—
|
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: one of Plautus’s later plays | Statement: [Rudens, locationInPlautusCorpus, one of Plautus’s later plays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInPlautusCorpus Context triple: [Rudens, locationInPlautusCorpus, one of Plautus’s later plays]
-
A.
placeInApuleiusCorpus
Indicates that a given text or passage occurs within the works that make up the Apuleius corpus.
-
B.
positionInAuthorOeuvre
Indicates the relative placement or order of a work within an author's overall body of work.
-
C.
locationOfPassage
Indicates the place or area through which a passage, route, or transit occurs or is situated.
-
D.
roleInAnalects
Indicates that one entity has a specific role, function, or status within the context of the Analects.
-
E.
workInPlatoCorpus
Indicates that an entity is a work that appears within the corpus of texts attributed to Plato.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0349d158b881908bfbdb501ea565ee |
completed | May 12, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_6a034750e3d48190a88ee3604a36b46d |
completed | May 12, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_6a0349d09ba88190918a4205de46638f |
completed | May 12, 2026, 3:40 p.m. |
Created at: May 1, 2026, 1:21 a.m.