Triple
T27003750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wietze (Örtze) |
E680181
|
entity |
| Predicate | isUpperReachOf |
P161761
|
FINISHED |
| Object | Örtze |
—
|
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: Örtze | Statement: [Wietze (Örtze), isUpperReachOf, Örtze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUpperReachOf Context triple: [Wietze (Örtze), isUpperReachOf, Örtze]
-
A.
hasLongerReachThan
Indicates that one entity can extend, influence, or physically reach farther than another entity.
-
B.
canReach
Indicates that one entity is able to access, arrive at, or establish a path to another entity.
-
C.
hasUpperReachesCharacter
Indicates that an entity’s upper reaches or uppermost parts possess a particular characteristic or quality.
-
D.
hasReach
Indicates that one entity is able to extend its influence, access, or physical span to another entity or area.
-
E.
isElevatedAbove
Indicates that one entity is positioned at a higher vertical level or altitude 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621d06a7c81908f80d005079262fd |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 27, 2026, 6:59 a.m.