Triple
T26864809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotes Kloster |
E676435
|
entity |
| Predicate | liegtAm |
P161973
|
FINISHED |
| Object | Fluss Dunajec |
—
|
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: Fluss Dunajec | Statement: [Rotes Kloster, liegtAm, Fluss Dunajec]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liegtAm Context triple: [Rotes Kloster, liegtAm, Fluss Dunajec]
-
A.
liesIn
Indicates that one entity is located within the spatial, geographical, or conceptual boundaries of another entity.
-
B.
liesOnBorderOf
Indicates that one entity is located along or directly adjacent to the boundary line separating it from another entity.
-
C.
liesOutside
Indicates that one entity is located entirely beyond the spatial or conceptual boundary of another entity.
-
D.
liesToThe
Indicates that one entity intentionally provides false or misleading information to another entity.
-
E.
liesBelow
Indicates that one entity is positioned at a lower vertical level than another entity.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f62081136c81909de8090b1d6c1ac5 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fd5442081908ca677a9c81dcb3f |
completed | May 2, 2026, 4:01 p.m. |
Created at: April 27, 2026, 5:28 a.m.