Triple
T4758364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slaughter of the Suitors |
E105641
|
entity |
| Predicate | hasKeyAction |
P58322
|
FINISHED |
| Object | Odysseus locks the doors of the hall |
—
|
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: Odysseus locks the doors of the hall | Statement: [Slaughter of the Suitors, hasKeyAction, Odysseus locks the doors of the hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyAction Context triple: [Slaughter of the Suitors, hasKeyAction, Odysseus locks the doors of the hall]
-
A.
hasKeyEvent
Indicates that an entity includes, is associated with, or is characterized by a significant or defining event.
-
B.
hasKeyActivity
Indicates that an entity is associated with or performs a primary or central activity.
-
C.
hasActionType
Indicates that an action or event is classified as belonging to a specific type or category of actions.
-
D.
hasKeyboard
Indicates that one entity possesses or is equipped with a keyboard as a component or accessory.
-
E.
hasKeyActor
Indicates that an entity plays a primary or central role (a key actor) in relation to another entity or context.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:20 p.m.