Triple
T10671037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frankfurt public transport network |
E251484
|
entity |
| Predicate | includesLineType |
P47205
|
FINISHED |
| Object | U-Bahn line |
—
|
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: U-Bahn line | Statement: [Frankfurt public transport network, includesLineType, U-Bahn line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesLineType Context triple: [Frankfurt public transport network, includesLineType, U-Bahn line]
-
A.
lineType
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
-
B.
servesLineType
chosen
Indicates that a service or entity operates or supports a specific type or category of line (e.g., transport, communication, or utility line).
-
C.
lineIncludes
Indicates that a specific line (such as a text line, code line, or route segment) contains or encompasses a given element or component.
-
D.
servedLineType
Indicates the type or category of service line associated with or provided in a given context.
-
E.
isLinedWith
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6f8648a248190a3bd284c569152e4 |
completed | April 9, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:09 p.m.