Triple
T13392766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meisner technique |
E319616
|
entity |
| Predicate | coreExercise |
P109743
|
FINISHED |
| Object | repetition exercise |
—
|
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: repetition exercise | Statement: [Meisner technique, coreExercise, repetition exercise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreExercise Context triple: [Meisner technique, coreExercise, repetition exercise]
-
A.
exerciseOf
Indicates the performance or carrying out of a right, power, function, or activity by an entity.
-
B.
keyExercise
Indicates that an exercise is a primary or essential component within a larger training, practice, or instructional context.
-
C.
alsoExercises
Indicates that one entity engages in physical exercise in addition to, or alongside, another referenced entity.
-
D.
freeExerciseTest
Indicates a legal assessment of whether a law or government action improperly burdens or restricts an individual’s or group’s free exercise of religion.
-
E.
exercise
Indicates that an entity engages in physical activity or training, typically to improve health, fitness, or performance.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d74e5881909828854bba7d9a87 |
completed | April 12, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:34 p.m.