Triple
T18127797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challenge Roth triathlon |
E433925
|
entity |
| Predicate | runCourseFeature |
P26149
|
FINISHED |
| Object | sections along the Main-Danube Canal |
—
|
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: sections along the Main-Danube Canal | Statement: [Challenge Roth triathlon, runCourseFeature, sections along the Main-Danube Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runCourseFeature Context triple: [Challenge Roth triathlon, runCourseFeature, sections along the Main-Danube Canal]
-
A.
courseSetupCharacteristic
chosen
Indicates a defining setup-related property or configuration aspect associated with a course.
-
B.
course
Indicates that an entity is an academic class or unit of instruction offered within an educational program.
-
C.
courseSetting
Indicates the context or environment in which a course is delivered or conducted.
-
D.
courseUse
Indicates that a course employs, incorporates, or makes use of a particular resource, tool, or material in its instruction or structure.
-
E.
trainingComponent
Indicates that one entity functions as a training-related part, module, or element within a larger training process or system involving 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddef4cd88190b16ef0d6ed3968c6 |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.