Triple
T12639462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frankfurt U-Bahn |
E301853
|
entity |
| Predicate | primaryCityCenterAxis |
P79159
|
FINISHED |
| Object | A route |
—
|
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: A route | Statement: [Frankfurt U-Bahn, primaryCityCenterAxis, A route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCityCenterAxis Context triple: [Frankfurt U-Bahn, primaryCityCenterAxis, A route]
-
A.
cityAxis
chosen
Indicates a primary directional or structural line that organizes or defines the layout and orientation of a city.
-
B.
notableCityCenter
Indicates that a location serves as a prominent or significant central area within a city.
-
C.
primaryCity
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
-
D.
isTransportCenterOf
Indicates that a location functions as a primary hub or central node for transportation activities serving another area or network.
-
E.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:16 p.m.