Triple
T33483456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin–Munich corridor |
E857542
|
entity |
| Predicate | hasRailAxis |
P191914
|
FINISHED |
| Object | Berlin–Munich high-speed railway |
—
|
NE NERFINISHED |
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: Berlin–Munich high-speed railway | Statement: [Berlin–Munich corridor, hasRailAxis, Berlin–Munich high-speed railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailAxis Context triple: [Berlin–Munich corridor, hasRailAxis, Berlin–Munich high-speed railway]
-
A.
hasRail
Indicates that something is equipped with, includes, or is connected to a rail or rail system.
-
B.
hasRailConfiguration
Indicates that an entity is associated with, or characterized by, a particular arrangement or setup of rails.
-
C.
hasRailMode
Indicates that an entity is associated with or supports transportation via rail-based modes (such as trains, trams, or subways).
-
D.
hasAccessoryRail
Indicates that an object is equipped with or includes an additional rail or mounting interface used to attach accessories.
-
E.
hasRailSymbol
Indicates that an entity is associated with or represented by a specific rail-related symbol or icon.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69fcef636dfc819085cf91323f2e4edd |
completed | May 7, 2026, 8 p.m. |
Created at: May 1, 2026, 1:38 a.m.