Triple
T18780454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form II Makashi |
E459240
|
entity |
| Predicate | typicalGuard |
P132982
|
FINISHED |
| Object | one-handed fencing-style stance |
—
|
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: one-handed fencing-style stance | Statement: [Form II Makashi, typicalGuard, one-handed fencing-style stance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGuard Context triple: [Form II Makashi, typicalGuard, one-handed fencing-style stance]
-
A.
guard
Indicates that one entity protects, watches over, or defends another entity or resource from harm, intrusion, or unauthorized access.
-
B.
guardian
Indicates a protective or custodial relationship in which one entity is responsible for the care, safety, or oversight of another.
-
C.
typicalGoing
Indicates that an entity is engaged in or undergoing a normal, expected instance of going or movement from one place to another.
-
D.
typicalGear
Indicates that the object represents the usual or standard equipment or gear commonly associated with the subject.
-
E.
guardType
Indicates the specific kind or category of guarding role or protection associated with an entity.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933e35a481908c21f7f488e1dd99 |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:52 a.m.