Triple
T36374858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altenwerder |
E895870
|
entity |
| Predicate | hasPortFacilityType |
P45226
|
FINISHED |
| Object | Deep-water container terminal |
—
|
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: Deep-water container terminal | Statement: [Altenwerder, hasPortFacilityType, Deep-water container terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortFacilityType Context triple: [Altenwerder, hasPortFacilityType, Deep-water container terminal]
-
A.
typeOfPortFacility
chosen
Indicates that one port facility is classified as a specific type or category of port facility in relation to another.
-
B.
hasPortType
Indicates that an entity is associated with, or characterized by, a specific type or category of port.
-
C.
hasPortRole
Indicates that an entity participates in a port with a specified functional or operational role.
-
D.
hasPortCapability
Indicates that an entity possesses the ability or feature to support, provide, or utilize a specific type of port or port-related function.
-
E.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff84202eb081908ae21a54a4414d68 |
completed | May 9, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69ff833065e4819098579129d4ee17d3 |
completed | May 9, 2026, 6:55 p.m. |
Created at: May 3, 2026, 4:10 p.m.