Triple
T35238994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commune of Lenningen |
E1017457
|
entity |
| Predicate | borderedByNaturalFeature |
P122362
|
FINISHED |
| Object | Moselle River |
—
|
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: Moselle River | Statement: [Commune of Lenningen, borderedByNaturalFeature, Moselle River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderedByNaturalFeature Context triple: [Commune of Lenningen, borderedByNaturalFeature, Moselle River]
-
A.
borderNature
Indicates the type or character of a border between entities, such as whether it is natural, political, administrative, or of another specified nature.
-
B.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
C.
countryBorderFeatureOf
Indicates that a geographical feature (such as a river, mountain range, or coastline) serves as or is part of the border of a country.
-
D.
borderRiverValleyOf
Indicates that a river forms or runs along the boundary of a valley, marking its border.
-
E.
borderingWaters
chosen
Indicates that a geographic area directly touches or is adjacent to a particular body of water.
- 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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: May 3, 2026, 4:02 p.m.