Triple
T38223095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German ICE |
E1012064
|
entity |
| Predicate | topSpeedInService_kmh |
P2096
|
FINISHED |
| Object | 300 |
—
|
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: 300 | Statement: [German ICE, topSpeedInService_kmh, 300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topSpeedInService_kmh Context triple: [German ICE, topSpeedInService_kmh, 300]
-
A.
designedSpeedKmH
Indicates the maximum speed in kilometers per hour that something is intended or engineered to achieve under its design specifications.
-
B.
designedServiceSpeed
Indicates the intended or specified operational speed at which a service is designed to function.
-
C.
maxSpeed
chosen
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
D.
speedOfHighSpeedTrain
Indicates the velocity at which a high-speed train is traveling.
-
E.
hasTopSpeedSection
Indicates that an entity includes or is associated with a segment or portion where the maximum or top speed is defined, reached, or relevant.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.