Triple
T21887383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | seventh labour of Heracles |
E540440
|
entity |
| Predicate | heroUsesMethod |
P35675
|
FINISHED |
| Object | overpowers the bull by physical strength |
—
|
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: overpowers the bull by physical strength | Statement: [seventh labour of Heracles, heroUsesMethod, overpowers the bull by physical strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroUsesMethod Context triple: [seventh labour of Heracles, heroUsesMethod, overpowers the bull by physical strength]
-
A.
hasProtagonistAbility
Indicates that a protagonist possesses a specific ability, power, or special skill.
-
B.
methodOfCombat
chosen
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
-
C.
usedByCharacter
Indicates that something (such as an item, ability, or resource) is utilized or employed by a particular character.
-
D.
methodOfDefeat
Indicates the specific way or technique by which one entity defeats or overcomes another.
-
E.
usedMethodOfKilling
Indicates that one entity employed a particular method or means to carry out a killing of 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ed35948190bbffba2c40029eee |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.