Triple
T1742715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daredevils of Sassoun |
E38266
|
entity |
| Predicate | containsMotive |
P15083
|
FINISHED |
| Object | superhuman 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: superhuman strength | Statement: [Daredevils of Sassoun, containsMotive, superhuman strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMotive Context triple: [Daredevils of Sassoun, containsMotive, superhuman strength]
-
A.
hasMotiveElement
chosen
Indicates that one entity includes, specifies, or is characterized by a particular motive-related component or factor in a broader relationship or action.
-
B.
motive
Indicates the underlying reason, intention, or driving force that explains why an entity performs or is associated with a particular action or event.
-
C.
motivationFor
Indicates that one entity serves as the reason, drive, or incentive behind another entity’s action, state, or occurrence.
-
D.
motivated
Indicates that one entity provides a reason, drive, or incentive that causes another entity to act or behave in a certain way.
-
E.
hasPartInMotto
Indicates that something is included as a component or element within a motto.
- 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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab630e7d008190a8c673665d9672bb |
completed | March 6, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69aa61c5a18481909bc49e0c54d64314 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.