Triple
T9495390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trave |
E228990
|
entity |
| Predicate | formsEstuaryType |
P33342
|
FINISHED |
| Object | fjord-like estuary near Travemünde |
—
|
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: fjord-like estuary near Travemünde | Statement: [Trave, formsEstuaryType, fjord-like estuary near Travemünde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsEstuaryType Context triple: [Trave, formsEstuaryType, fjord-like estuary near Travemünde]
-
A.
formsEstuary
chosen
Indicates that a river or watercourse meets a larger body of water in such a way that it creates or constitutes an estuary.
-
B.
hasEstuaryType
Indicates the specific type or classification of an estuary associated with a given water body or location.
-
C.
hasEstuaryAt
Indicates that a river or watercourse flows into and meets a larger body of water (such as a sea, ocean, or lake) at a specific location.
-
D.
hasEstuaryNear
Indicates that the estuary of a water body is located in close proximity to a specified place or feature.
-
E.
formsWetland
Indicates that one entity creates, develops, or gives rise to a wetland environment in relation to another entity or location.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd95eb87b081908fc7255598cd9a24 |
completed | April 1, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:56 p.m.