Triple
T32966658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amphitruo |
E843388
|
entity |
| Predicate | hasServantCharacter |
P4079
|
FINISHED |
| Object | Sosia |
—
|
NE NERFINISHED |
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: Sosia | Statement: [Amphitruo, hasServantCharacter, Sosia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServantCharacter Context triple: [Amphitruo, hasServantCharacter, Sosia]
-
A.
hasServant
chosen
Indicates that one entity has another entity serving it in a subordinate or attendant role.
-
B.
hasEnslavedCharacter
Indicates that one entity has held another entity in a state of slavery or forced servitude.
-
C.
hasBailiffCharacter
Indicates that one entity is characterized as, or fulfills the role of, a bailiff in relation to another entity.
-
D.
hasMonkCharacter
Indicates that an entity includes or features a character whose role or identity is that of a monk.
-
E.
hasPuppetCharacter
Indicates that one entity features, includes, or is associated with a particular puppet character as part of its content or composition.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: May 1, 2026, 1:21 a.m.