Triple
T16654578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuremberg–Ingolstadt high-speed railway |
E404693
|
entity |
| Predicate | travelTimeNurembergMunich |
P46906
|
FINISHED |
| Object | about 1 hour |
—
|
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: about 1 hour | Statement: [Nuremberg–Ingolstadt high-speed railway, travelTimeNurembergMunich, about 1 hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelTimeNurembergMunich Context triple: [Nuremberg–Ingolstadt high-speed railway, travelTimeNurembergMunich, about 1 hour]
-
A.
distanceToMunich
Indicates the spatial distance between a given entity’s location and the city of Munich.
-
B.
distanceToNuremberg
Indicates the spatial distance between a given entity and the location of Nuremberg.
-
C.
transportProject
Indicates a project whose primary purpose is to plan, build, improve, or manage transportation systems, services, or infrastructure.
-
D.
travelTimeTypical
chosen
Indicates the usual or expected amount of time it takes to travel between two locations under normal conditions.
-
E.
travelTimeByFerry
Indicates the duration required to travel between two locations specifically using a ferry as the mode of transportation.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bf92de48190aaae3e93039b17f3 |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.