Triple
T16533164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RegionalBahn |
E401617
|
entity |
| Predicate | relativeStopPatternComparedTo |
P123926
|
FINISHED |
| Object | more stops 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: more stops than Regional-Express | Statement: [RegionalBahn, relativeStopPatternComparedTo, more stops than Regional-Express]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeStopPatternComparedTo Context triple: [RegionalBahn, relativeStopPatternComparedTo, more stops than Regional-Express]
-
A.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
B.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to another entity.
-
C.
isRelativeTo
Indicates that one entity has a familial or kinship relationship to another entity.
-
D.
isRelatively
Indicates that one entity is being described, measured, or evaluated in relation to another entity or reference point, rather than in absolute terms.
-
E.
relativePlaysIn
Indicates that a person has a relative who plays in (is a member of or participates in) a specified team, group, or organization.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:15 a.m.