Triple
T4896882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemean lion myth |
E109703
|
entity |
| Predicate | heroServitudeContext |
P60513
|
FINISHED |
| Object | penance for killing his family |
—
|
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: penance for killing his family | Statement: [Nemean lion myth, heroServitudeContext, penance for killing his family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroServitudeContext Context triple: [Nemean lion myth, heroServitudeContext, penance for killing his family]
-
A.
hasServant
Indicates that one entity has another entity serving it in a subordinate or attendant role.
-
B.
rescuesContext
Indicates that one entity saves or delivers another entity from danger, harm, or a problematic situation within a specific contextual setting.
-
C.
hadTyrant
Indicates that an entity was ruled or dominated by a tyrant.
-
D.
servesAtThePleasureOf
Indicates that one entity holds a position or role that can be terminated at any time by another entity, typically at the discretion or will of that other entity.
-
E.
hasEnslavedCharacter
Indicates that one entity has held another entity in a state of slavery or forced servitude.
- 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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706245e48190a61d573438461c30 |
completed | March 20, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69bd6c306b188190a08a7856beb76db4 |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd7060f9988190afdf98eb0a38515d |
completed | March 20, 2026, 4:05 p.m. |
Created at: March 20, 2026, 1:28 p.m.