Triple
T8713186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germany–Austria border |
E206828
|
entity |
| Predicate | includesLakeBoundary |
P61468
|
FINISHED |
| Object | Lake Constance region |
—
|
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: Lake Constance region | Statement: [Germany–Austria border, includesLakeBoundary, Lake Constance region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesLakeBoundary Context triple: [Germany–Austria border, includesLakeBoundary, Lake Constance region]
-
A.
hasLakeThatRepresents
Indicates a relationship where a lake serves as a symbolic or representative feature for something, such as a place, concept, or entity.
-
B.
isInLake
Indicates that one entity is located within the body of water defined as a lake.
-
C.
isLakeType
Indicates that one entity is a specific type or category of lake in relation to another entity.
-
D.
usesLakeFor
Indicates that an entity utilizes a lake as a resource or setting for some purpose, activity, or function.
-
E.
shareWaterBoundary
chosen
Indicates that two entities are adjacent to each other with a shared boundary formed by a 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cd522a88190a32facd86206af66 |
completed | March 31, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.