Triple
T4896869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemean lion myth |
E109703
|
entity |
| Predicate | postCombatAction |
P19109
|
FINISHED |
| Object | Heracles skins lion |
—
|
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: Heracles skins lion | Statement: [Nemean lion myth, postCombatAction, Heracles skins lion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postCombatAction Context triple: [Nemean lion myth, postCombatAction, Heracles skins lion]
-
A.
postConquestUse
Indicates how something is used, occupied, or functionally repurposed after a conquest has taken place.
-
B.
afterConquest
Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
-
C.
aftermathOf
Indicates that one event, state, or condition occurs as a consequence or result following another event.
-
D.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
E.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
- F. None of above.
Provenance (3 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. |
Created at: March 20, 2026, 1:28 p.m.