Triple
T26864831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotes Kloster |
E676435
|
entity |
| Predicate | liegtNahe |
P61362
|
FINISHED |
| Object | Grenzort Sromowce Niżne (Polen) |
—
|
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: Grenzort Sromowce Niżne (Polen) | Statement: [Rotes Kloster, liegtNahe, Grenzort Sromowce Niżne (Polen)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liegtNahe Context triple: [Rotes Kloster, liegtNahe, Grenzort Sromowce Niżne (Polen)]
-
A.
nearbyTo
chosen
Indicates that one entity is located close in distance or position to another entity.
-
B.
near
Indicates that one entity is located at a short distance from another entity in space or position.
-
C.
meetsNear
Indicates that two entities meet or come together at a location that is in close proximity to a specified reference point or area.
-
D.
liegtAm
Indicates that one entity is located on, by, or along another entity (such as a place lying on a river, coast, or route).
-
E.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 5:28 a.m.