Triple
T913003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Penelopiad |
E19703
|
entity |
| Predicate | questionedCharacter |
P21473
|
FINISHED |
| Object | heroic image of Odysseus |
—
|
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: heroic image of Odysseus | Statement: [The Penelopiad, questionedCharacter, heroic image of Odysseus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questionedCharacter Context triple: [The Penelopiad, questionedCharacter, heroic image of Odysseus]
-
A.
subjectOfInquest
Indicates that an entity is the focus or target of a formal inquest or official investigative proceeding.
-
B.
suspectedPerpetrator
Indicates that an entity is believed or alleged to be the person responsible for committing a particular harmful or illegal act.
-
C.
isSoughtBy
Indicates that one entity is actively being searched for, pursued, or desired by another entity.
-
D.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
E.
firstAccused
Indicates that the subject is the primary or earliest individual formally charged or blamed in a particular case or incident.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b2f605bc8190a5245aa2ca55cf43 |
completed | March 1, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69a4b2918ea881908698020b995a8eae |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b2f4e3fc81908c8a2d1fbef9c5d2 |
completed | March 1, 2026, 9:43 p.m. |
Created at: March 1, 2026, 7:39 p.m.