Triple
T6708899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mannheim |
E153078
|
entity |
| Predicate | hasHarborRanking |
P72566
|
FINISHED |
| Object | one of the largest inland ports in Europe |
—
|
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: one of the largest inland ports in Europe | Statement: [Mannheim, hasHarborRanking, one of the largest inland ports in Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHarborRanking Context triple: [Mannheim, hasHarborRanking, one of the largest inland ports in Europe]
-
A.
hasHarbor
Indicates that a place possesses or contains a harbor for docking or sheltering vessels.
-
B.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
C.
hasRankingCategory
Indicates that an entity is associated with a particular ranking category or tier within an ordered classification system.
-
D.
hasHarborFeature
Indicates that something possesses or includes a specific harbor-related characteristic, structure, or facility.
-
E.
hasPrivateHarbour
Indicates that an entity possesses or is associated with its own exclusive harbour not shared with the general public.
- F. None of above. chosen
Provenance (4 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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d16897e48190b43eda2206b14d6a |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d089c7488190a00853fb12f53b2a |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1668a7c8190ae93951f9ba2df10 |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:06 p.m.