Triple
T5049658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LernaeanHydra |
E113751
|
entity |
| Predicate | defeatedByMethod |
P44055
|
FINISHED |
| Object | decapitationAndCauterization |
—
|
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: decapitationAndCauterization | Statement: [LernaeanHydra, defeatedByMethod, decapitationAndCauterization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defeatedByMethod Context triple: [LernaeanHydra, defeatedByMethod, decapitationAndCauterization]
-
A.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
B.
methodOfDefeat
chosen
Indicates the specific way or technique by which one entity defeats or overcomes another.
-
C.
overthrowMethod
Indicates the method or means by which an overthrow (such as of a government, leader, or regime) is carried out.
-
D.
method
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
E.
usesMethods
Indicates that one entity employs, applies, or relies on specific methods or techniques to perform an action or achieve a result.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.