Triple
T13114041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Märkisch-Oderland |
E311046
|
entity |
| Predicate | hasBorderLengthWithOder |
P39383
|
FINISHED |
| Object | significant section of Oder River |
—
|
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: significant section of Oder River | Statement: [Märkisch-Oderland, hasBorderLengthWithOder, significant section of Oder River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderLengthWithOder Context triple: [Märkisch-Oderland, hasBorderLengthWithOder, significant section of Oder River]
-
A.
hasBorderLengthCharacteristic
chosen
Indicates that a border is associated with a specific length-related property or characteristic.
-
B.
hasBorderElement
Indicates that one entity includes or is associated with another entity that forms part of its boundary or edge.
-
C.
hasBorderDirection
Indicates that one entity’s border lies in, or is oriented toward, a specified cardinal or relative direction with respect to another entity.
-
D.
hasBorderCode
Indicates that there is an associated code or identifier specifying the type or status of a border between entities.
-
E.
hasBorderRelation
Indicates that one entity shares a boundary or border with another entity.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9817f8ee8819084078b4bec5e4f18 |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:06 p.m.