Triple
T32966729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pseudolus |
E843390
|
entity |
| Predicate | characterRoleOfPseudolus |
P199087
|
FINISHED |
| Object | clever slave |
—
|
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: clever slave | Statement: [Pseudolus, characterRoleOfPseudolus, clever slave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterRoleOfPseudolus Context triple: [Pseudolus, characterRoleOfPseudolus, clever slave]
-
A.
voiceTypeOfCharacter Polinesso
Indicates that the specified voice type is the vocal classification assigned to the character Polinesso.
-
B.
theaterRole
Indicates that an entity holds or performs a specific role or character in a theatrical production in relation to another entity (such as a play or performance).
-
C.
relationshipToTrinculo
Indicates the specific type of relationship or connection that one entity has to the entity named Trinculo.
-
D.
roleInFamousPlay
Indicates that an entity portrays or has portrayed a specific character in a well-known theatrical play.
-
E.
roleInRomeoAndJuliet
Indicates the specific character or part that an entity plays in the work "Romeo and Juliet."
- 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_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
| PDg | Predicate description generation | batch_69ff1e3d5f488190ba6e4f024128fb99 |
completed | May 9, 2026, 11:45 a.m. |
Created at: May 1, 2026, 1:21 a.m.