Triple
T528158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordic combined |
E10968
|
entity |
| Predicate | jumpCount |
P11575
|
FINISHED |
| Object | usually 1 or 2 competition jumps |
—
|
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: usually 1 or 2 competition jumps | Statement: [Nordic combined, jumpCount, usually 1 or 2 competition jumps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jumpCount Context triple: [Nordic combined, jumpCount, usually 1 or 2 competition jumps]
-
A.
movementCount
Indicates the number of times a movement or relocation action has occurred between the related entities.
-
B.
movementNumber
Indicates the specific sequential position of a movement within a larger multi-movement work or performance.
-
C.
roundCount
chosen
Indicates the number of discrete rounds or iterations that have occurred or are allocated within a process, event, or interaction.
-
D.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
E.
arrowCount
Indicates the number of arrows associated with or involved in a given entity or interaction.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d2851c81908129f7da932ab7b3 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f01ac3ec8190a94a05955532c7fa |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.