Triple
T16533177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RegionalBahn |
E401617
|
entity |
| Predicate | higherLevelCategory |
P58049
|
FINISHED |
| Object | public transport in Germany |
—
|
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: public transport in Germany | Statement: [RegionalBahn, higherLevelCategory, public transport in Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherLevelCategory Context triple: [RegionalBahn, higherLevelCategory, public transport in Germany]
-
A.
highestCategory
Indicates that the related entity is the topmost or most specific category to which another entity is ultimately classified or assigned.
-
B.
coreCategory
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
-
C.
agingCategory
Indicates the classification of an entity based on its stage or degree of aging.
-
D.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
-
E.
generalCategory
chosen
Indicates that one entity is classified as a broad or overarching category to which the other entity belongs.
- 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.