Triple
T29028961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wie aus der Ferne (No. 17) |
E737673
|
entity |
| Predicate | cycleSize |
P97058
|
FINISHED |
| Object | 18 movements |
—
|
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: 18 movements | Statement: [Wie aus der Ferne (No. 17), cycleSize, 18 movements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cycleSize Context triple: [Wie aus der Ferne (No. 17), cycleSize, 18 movements]
-
A.
cycleType
Indicates the specific kind or category of cycle involved in a repeated or cyclical process or relationship.
-
B.
typicalNumberOfCycles
chosen
Indicates the usual or characteristic count of cycles associated with an entity, process, or event.
-
C.
cycleWith
Indicates that two or more entities participate together in a cycling activity, such as riding bicycles along the same route or at the same time.
-
D.
cycleConsistsOf
Indicates that a cycle is composed of, or made up from, the specified component elements or segments.
-
E.
cycleBy
Indicates that one entity moves or travels by means of riding a bicycle (or similar cycle) in relation to another entity or context.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 9:54 a.m.