Triple
T16533163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RegionalBahn |
E401617
|
entity |
| Predicate | relativeSpeedComparedTo |
P106461
|
FINISHED |
| Object | slower than Regional-Express |
—
|
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: slower than Regional-Express | Statement: [RegionalBahn, relativeSpeedComparedTo, slower than Regional-Express]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeSpeedComparedTo Context triple: [RegionalBahn, relativeSpeedComparedTo, slower than Regional-Express]
-
A.
relativeSpeedCategory
chosen
Indicates the categorized comparison of one entity’s speed relative to another (e.g., slower, similar, or faster).
-
B.
relativeMotionType
Indicates the type or nature of motion occurring between two entities relative to one another.
-
C.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
D.
hasRelativeProminenceComparedTo
Indicates that one entity has a greater, lesser, or otherwise specified level of prominence or importance when compared to another entity.
-
E.
rankComparedTo
Indicates the relative ordering or position of one entity in comparison to another based on a specified ranking criterion.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed97b0881909de106418aca8180 |
completed | April 18, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.