Triple
T6230984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regionalbahn |
E139350
|
entity |
| Predicate | categoryDefinedBy |
P69644
|
FINISHED |
| Object | German railway timetables |
—
|
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: German railway timetables | Statement: [Regionalbahn, categoryDefinedBy, German railway timetables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: categoryDefinedBy Context triple: [Regionalbahn, categoryDefinedBy, German railway timetables]
-
A.
categoryDefinedIn
Indicates that a category is formally specified or established within a particular source, context, or definitional framework.
-
B.
classificationTerm
Indicates that one entity serves as a categorical label or type used to classify or group another entity.
-
C.
categoryDistinguishedFrom
Indicates that one category is explicitly distinguished from another, clarifying that they are separate and should not be confused.
-
D.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
-
E.
baseDefinedBy
Indicates that something’s foundational properties, structure, or interpretation are determined or specified by a particular base or underlying system.
- 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062ec5be4819084d6df2e8dd2a542 |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c05601de6481909d0880048fd7b49a |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c05707d5408190a1d0fd80414ad957 |
completed | March 22, 2026, 8:54 p.m. |
Created at: March 22, 2026, 4:22 p.m.