Triple
T38177462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bäveån |
E1000254
|
entity |
| Predicate | hasMouthEnvironment |
P200984
|
FINISHED |
| Object | marine coastal environment |
—
|
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: marine coastal environment | Statement: [Bäveån, hasMouthEnvironment, marine coastal environment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMouthEnvironment Context triple: [Bäveån, hasMouthEnvironment, marine coastal environment]
-
A.
hasTypeOfMouth
Indicates that an entity possesses a mouth characterized by a specific type or form.
-
B.
hasMouthCount
Indicates the number of mouths that an entity possesses.
-
C.
hasScenicMouth
Indicates that an entity’s mouth is visually attractive or aesthetically pleasing to look at.
-
D.
containsMouthOf
Indicates that one entity geographically includes or encompasses the mouth (outflow point) of another entity, such as a river or stream.
-
E.
hasPortNearMouth
Indicates that an entity possesses a port or opening located close to its mouth region.
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ffbf84f4948190b41a7bba07ae61ec |
completed | May 9, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69ffbf0a59f88190870dbe25d8a63a00 |
completed | May 9, 2026, 11:11 p.m. |
| PDg | Predicate description generation | batch_69ffbf8402c48190a9bf3c3fcb874508 |
completed | May 9, 2026, 11:13 p.m. |
Created at: May 3, 2026, 4:29 p.m.