Triple
T20771915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICE 2 |
E511256
|
entity |
| Predicate | primaryRoutes |
P141455
|
FINISHED |
| Object | German high-speed lines |
—
|
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 high-speed lines | Statement: [ICE 2, primaryRoutes, German high-speed lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoutes Context triple: [ICE 2, primaryRoutes, German high-speed lines]
-
A.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
B.
primaryRouteFrom
Indicates that one entity serves as the main or preferred route originating from another entity.
-
C.
primaryRouteType
Indicates the main category or kind of route associated with an entity, such as its primary mode, path, or routing classification.
-
D.
firstRoutes
Indicates that one route or path is the initial or primary route taken or assigned among a set of possible routes.
-
E.
primaryRailLinkFor
Indicates that one entity serves as the main or principal rail connection or route for another entity.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2681ff88190bfe5938c2db6b2c4 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:37 p.m.