Triple
T13212771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimura lock |
E314534
|
entity |
| Predicate | targetsJoint |
P860
|
FINISHED |
| Object | shoulder joint |
—
|
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: shoulder joint | Statement: [Kimura lock, targetsJoint, shoulder joint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsJoint Context triple: [Kimura lock, targetsJoint, shoulder joint]
-
A.
targetsBody
Indicates that one entity is directed at, aimed at, or focused on affecting the body of another entity.
-
B.
neckJoint
Indicates a joint or connection located at or functioning as the neck between two body parts or structural elements.
-
C.
target
chosen
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
D.
aimedAtBy
Indicates that one entity serves as the target or goal toward which another entity directs an action, intention, or focus.
-
E.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9f0f148190a0698ef27573c885 |
completed | April 10, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:17 p.m.