Triple
T22767722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeet Kune Do |
E563171
|
entity |
| Predicate | usesGuard |
P48627
|
FINISHED |
| Object | lead-hand forward guard |
—
|
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: lead-hand forward guard | Statement: [Jeet Kune Do, usesGuard, lead-hand forward guard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGuard Context triple: [Jeet Kune Do, usesGuard, lead-hand forward guard]
-
A.
guardType
chosen
Indicates the specific kind or category of guarding role or protection associated with an entity.
-
B.
guardFeature
Indicates that one entity protects, secures, or restricts access to a particular feature of another entity.
-
C.
guardedAs
Indicates that one entity is protected, watched over, or kept secure in the role or capacity specified by another entity.
-
D.
hasGatekeeper
Indicates that one entity serves as a controlling or mediating gatekeeper for access to another entity.
-
E.
hasGuardCharacter
Indicates that one entity serves as a guard or protective character for 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_69e24552e11c81909c2d61578a558bd7 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17a81d3348190b005a43a5e03d406 |
completed | April 29, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:27 p.m.