Triple
T855110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Głogów |
E18473
|
entity |
| Predicate | isOnTransportRoute |
P11026
|
FINISHED |
| Object | Oder River waterway |
—
|
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: Oder River waterway | Statement: [Głogów, isOnTransportRoute, Oder River waterway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnTransportRoute Context triple: [Głogów, isOnTransportRoute, Oder River waterway]
-
A.
hasTransportRoute
chosen
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
B.
isPartOfRoute
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
C.
hasTransportHub
Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
-
D.
appliesToTransitLine
Indicates that a rule, condition, or characteristic is specifically associated with and relevant to a particular transit line.
-
E.
hasTransitFocus
Indicates that something is oriented toward, prioritizes, or is primarily concerned with transit or transportation services.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac3a48c08190b4677d825fcbfaf9 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa834a588190bca4a0eb83fb3eb6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.