Triple
T31526556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haren (Ems) |
E804360
|
entity |
| Predicate | hasInlandPort |
P87223
|
FINISHED |
| Object | Haren inland port |
—
|
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: Haren inland port | Statement: [Haren (Ems), hasInlandPort, Haren inland port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInlandPort Context triple: [Haren (Ems), hasInlandPort, Haren inland port]
-
A.
isInlandPort
Indicates that a port facility is located inland, away from the open sea, typically on a river, canal, or lake, while still serving maritime or shipping functions.
-
B.
linkedToInlandPort
chosen
Indicates a relationship where something has a direct connection or association with an inland port, such as for transport, logistics, or access purposes.
-
C.
isPortOf
Indicates that one location or facility serves as a port or harbor for another place, entity, or transportation route.
-
D.
hasInlandCity
Indicates that one entity has, contains, or is associated with a city located inland (away from the coast or major bodies of water).
-
E.
isHomePortOf
Indicates that a particular location serves as the primary base or port where a vessel or fleet is officially registered, stationed, or regularly returns.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
Created at: April 30, 2026, 9:59 p.m.