Triple
T29047942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogesnelheidslijn Zuid |
E735183
|
entity |
| Predicate | designedForSpeedClass |
P9902
|
FINISHED |
| Object | high-speed (≥250 km/h) |
—
|
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: high-speed (≥250 km/h) | Statement: [Hogesnelheidslijn Zuid, designedForSpeedClass, high-speed (≥250 km/h)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForSpeedClass Context triple: [Hogesnelheidslijn Zuid, designedForSpeedClass, high-speed (≥250 km/h)]
-
A.
speedClass
chosen
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
B.
designedSpeedKmH
Indicates the maximum speed in kilometers per hour that something is intended or engineered to achieve under its design specifications.
-
C.
designedServiceSpeed
Indicates the intended or specified operational speed at which a service is designed to function.
-
D.
speedClassMarking
Indicates how an entity is categorized or labeled according to its speed characteristics or performance class.
-
E.
designedForCompetition
Indicates that something was intentionally created or configured to be used in a competitive context or event.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 28, 2026, 10:06 a.m.