Triple
T4351016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lua (Hawaiian martial art) |
E98025
|
entity |
| Predicate | lethality |
P55695
|
FINISHED |
| Object | potentially lethal |
—
|
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: potentially lethal | Statement: [lua (Hawaiian martial art), lethality, potentially lethal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lethality Context triple: [lua (Hawaiian martial art), lethality, potentially lethal]
-
A.
willKill
Indicates that one entity is destined or intends to cause the death of another entity in the future.
-
B.
effectOfDeath
Indicates the causal impact or consequences that a death has on another entity, state, or process.
-
C.
deadliestIn
Indicates that something has the highest lethality or causes the most deaths within a specified context, group, or location.
-
D.
deathMethod
Indicates the specific way or means by which a death occurred.
-
E.
death
Indicates the event or state in which an entity ceases to live or exist, marking the end of its biological or functional processes.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351a99788819080b13a20124e49a0 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:15 p.m.