Triple
T15672296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemean Lion |
E377343
|
entity |
| Predicate | defeatedDespite |
P119701
|
FINISHED |
| Object | invulnerability of its hide |
—
|
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: invulnerability of its hide | Statement: [Nemean Lion, defeatedDespite, invulnerability of its hide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defeatedDespite Context triple: [Nemean Lion, defeatedDespite, invulnerability of its hide]
-
A.
defeat
Indicates that one entity wins against and overcomes another in a contest, conflict, or competition.
-
B.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
C.
defeatedInEvent
Indicates that one entity lost to another entity in the context of a specific event or competition.
-
D.
wasBeaten
Indicates that one entity defeated or physically overpowered another in a contest, conflict, or confrontation.
-
E.
defeatedCandidate
Indicates that one candidate has won an election or contest against another candidate, causing the other to lose.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f13b1b08190beabc9f4098aa096 |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:16 a.m.