Triple
T31371982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FSP |
E800186
|
entity |
| Predicate | belongsToCityTransportSystem |
P8428
|
FINISHED |
| Object | Frankfurt U-Bahn |
—
|
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: Frankfurt U-Bahn | Statement: [FSP, belongsToCityTransportSystem, Frankfurt U-Bahn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToCityTransportSystem Context triple: [FSP, belongsToCityTransportSystem, Frankfurt U-Bahn]
-
A.
partOfTransitSystem
chosen
Indicates that something is a component or segment within a larger transit or transportation system.
-
B.
appliesToTransitSystem
Indicates that something (such as a rule, policy, feature, or condition) is relevant or applicable to a particular transit or transportation system.
-
C.
associatedWithTransitSystem
Indicates that an entity has a connection or involvement with a particular transit or transportation system.
-
D.
usedByTransitSystem
Indicates that something is utilized or operated by a transit or public transportation system.
-
E.
belongsToUrbanCorridor
Indicates that something is part of, contained within, or functionally integrated into a continuous urban corridor or urbanized area.
- 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_69f224e6b7448190ac6bf97ad7364160 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: April 29, 2026, 9:18 p.m.