Triple
T22767721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeet Kune Do |
E563171
|
entity |
| Predicate | usesStance |
P8071
|
FINISHED |
| Object | on-guard stance influenced by fencing |
—
|
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: on-guard stance influenced by fencing | Statement: [Jeet Kune Do, usesStance, on-guard stance influenced by fencing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStance Context triple: [Jeet Kune Do, usesStance, on-guard stance influenced by fencing]
-
A.
bearerStance
Indicates the attitude, position, or viewpoint that the bearer holds toward a referenced subject or issue.
-
B.
hasFightingStance
chosen
Indicates that an entity adopts or is characterized by a particular combat or fighting posture.
-
C.
isStandOf
Indicates that one entity serves as the Stand (a supernatural or personified power) belonging to or associated with another entity.
-
D.
boxingStance
Indicates the specific posture or positioning a boxer adopts while preparing to fight or engage in boxing actions.
-
E.
stands
Indicates that an entity is in an upright position, typically supported by its feet or base, rather than sitting, lying, or moving.
- 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.