Triple
T13212807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimura lock |
E314534
|
entity |
| Predicate | setupFrom |
P28573
|
FINISHED |
| Object | failed armbar attempts |
—
|
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: failed armbar attempts | Statement: [Kimura lock, setupFrom, failed armbar attempts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setupFrom Context triple: [Kimura lock, setupFrom, failed armbar attempts]
-
A.
setUp
Indicates establishing, arranging, or preparing something so that it is ready for use or for a particular purpose.
-
B.
builtFrom
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
-
C.
typicalSetup
chosen
Indicates that an entity is arranged, configured, or organized in its standard or commonly used setup relative to another entity or context.
-
D.
frameworkEstablished
Indicates that a structured system of rules, guidelines, or components has been formally created and put in place to support or govern subsequent activities or relationships.
-
E.
implementedFrom
Indicates that one entity is realized, built, or executed based on the design, specification, or definition provided by 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.