Triple
T29607858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pisanio |
E754625
|
entity |
| Predicate | relationshipToPosthumus |
P203480
|
FINISHED |
| Object | servant and confidant |
—
|
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: servant and confidant | Statement: [Pisanio, relationshipToPosthumus, servant and confidant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToPosthumus Context triple: [Pisanio, relationshipToPosthumus, servant and confidant]
-
A.
posthumousAssociation
Indicates an association or connection between entities that is established, recognized, or relevant only after one of the entities has died.
-
B.
relationshipToPármeno
Indicates the specific type of personal or social relationship that one entity has to Pármeno.
-
C.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
-
D.
associatedWithDynasty
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
E.
isPosthumousNameOf
Indicates that one name is a posthumous title or designation that was given to and refers to a person after their death.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a018f9c7cf88190adc5daf3806f2077 |
completed | May 11, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_6a018ca4e0e481908091f0c1f8a4c31b |
completed | May 11, 2026, 8 a.m. |
| PDg | Predicate description generation | batch_6a018f9bd91c8190980967b4eef78a58 |
completed | May 11, 2026, 8:13 a.m. |
Created at: April 28, 2026, 6:26 p.m.