Triple
T19317478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ormond Hotel episode in Ulysses |
E483135
|
entity |
| Predicate | HomericFunction |
P135568
|
FINISHED |
| Object | temptation |
—
|
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: temptation | Statement: [Ormond Hotel episode in Ulysses, HomericFunction, temptation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HomericFunction Context triple: [Ormond Hotel episode in Ulysses, HomericFunction, temptation]
-
A.
eraOfMyth
Indicates a temporal relationship where an event, story, or phenomenon belongs to or takes place during a mythological or legendary era.
-
B.
goalInTrojanWar
Indicates that an entity’s objective, aim, or purpose is specifically directed toward or realized within the context of the Trojan War.
-
C.
roleInTrojanWar
Indicates the specific function, position, or part an entity played in the events of the Trojan War.
-
D.
AthenianCommander
Indicates that the subject serves as a military commander for the Athenians or the Athenian state.
-
E.
relationToOdysseus
Indicates the specific familial, social, or narrative relationship that one entity has to Odysseus.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d85046c81909d972a6b369b0c2b |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4e4709d4481908c280cdd2ac18977 |
completed | April 19, 2026, 2:19 p.m. |
Created at: April 10, 2026, 1:32 p.m.