Triple
T22827832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Furka Oberalp Railway |
E565707
|
entity |
| Predicate | hasRackSectionGradient |
P63610
|
FINISHED |
| Object | up to about 110 ‰ |
—
|
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: up to about 110 ‰ | Statement: [Furka Oberalp Railway, hasRackSectionGradient, up to about 110 ‰]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRackSectionGradient Context triple: [Furka Oberalp Railway, hasRackSectionGradient, up to about 110 ‰]
-
A.
hasGradientSection
Indicates that an entity includes a portion or segment where some property changes gradually rather than remaining constant.
-
B.
hasGradient
chosen
Indicates that one entity possesses or is characterized by a gradual change in value, intensity, or property across its extent or between two points.
-
C.
hasSectionColor
Indicates that an entity possesses a section (or part) characterized by a specific color.
-
D.
hasVerticalSection
Indicates that one entity possesses or includes a distinct vertical section or segment as part of its structure or representation.
-
E.
isMultiSectional
Indicates that something is composed of or divided into multiple distinct sections or parts.
- 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_69e24585ab1c81909b2b5065d15805d5 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2914188190be6cdbd8167cd806 |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:34 p.m.