Triple
T4350997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lua (Hawaiian martial art) |
E98025
|
entity |
| Predicate | combatRange |
P35675
|
FINISHED |
| Object | grappling |
—
|
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: grappling | Statement: [lua (Hawaiian martial art), combatRange, grappling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatRange Context triple: [lua (Hawaiian martial art), combatRange, grappling]
-
A.
frontArmorRange
Indicates the range or extent of protective armor coverage on the front-facing side of an entity.
-
B.
operationalRange
Indicates the span of conditions (such as distance, time, or environment) within which a system, device, or process can function effectively and safely.
-
C.
tieneAlcance
Indicates that something possesses or has a certain scope, reach, or range of effect in relation to something else.
-
D.
combatArm
Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
-
E.
methodOfCombat
chosen
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
- 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_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. |
Created at: March 12, 2026, 11:15 p.m.