Triple
T19134093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suitors of Penelope |
E468388
|
entity |
| Predicate | relationToOdysseus |
P134552
|
FINISHED |
| Object | usurpers of his household |
—
|
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: usurpers of his household | Statement: [Suitors of Penelope, relationToOdysseus, usurpers of his household]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToOdysseus Context triple: [Suitors of Penelope, relationToOdysseus, usurpers of his household]
-
A.
relationshipToHeracles
Indicates the specific familial or social relationship that an entity has to Heracles.
-
B.
relationshipToHecuba
Indicates a familial or social connection that an entity has with Hecuba.
-
C.
relationshipToDeianira
Indicates a specified type of relationship that one entity has to Deianira, such as familial, romantic, or social connection.
-
D.
poseidonRelation
Indicates a mythological or symbolic relationship involving Poseidon, such as kinship, patronage, or influence over another entity.
-
E.
relationshipToAeneas
Indicates the specific familial, social, or narrative relationship that one entity has to Aeneas.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3eb325081909035beefd1c9daf0 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:05 p.m.