Triple
T3174488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordic skiing |
E66428
|
entity |
| Predicate | trainingBenefit |
P27937
|
FINISHED |
| Object | cardiovascular fitness |
—
|
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: cardiovascular fitness | Statement: [Nordic skiing, trainingBenefit, cardiovascular fitness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainingBenefit Context triple: [Nordic skiing, trainingBenefit, cardiovascular fitness]
-
A.
training
Indicates that one entity is teaching, coaching, or otherwise helping another entity acquire or improve a skill, behavior, or capability.
-
B.
trainingLeadsTo
chosen
Indicates that a process of training results in or brings about a particular outcome, state, or effect.
-
C.
benefits
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
-
D.
trainingComponent
Indicates that one entity functions as a training-related part, module, or element within a larger training process or system involving another entity.
-
E.
trainingSupport
Indicates that one entity provides assistance, resources, or facilitation to help another entity conduct or participate in training activities.
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada670c800819098937783e2b05c7a |
completed | March 8, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.