Triple
T27381484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trubezh River |
E691241
|
entity |
| Predicate | hasNotableSettlementOnBank |
P16159
|
FINISHED |
| Object | Pereslavl-Zalessky |
—
|
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: Pereslavl-Zalessky | Statement: [Trubezh River, hasNotableSettlementOnBank, Pereslavl-Zalessky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSettlementOnBank Context triple: [Trubezh River, hasNotableSettlementOnBank, Pereslavl-Zalessky]
-
A.
hasCityOnBank
Indicates that a city is located on the bank of a particular river or body of water.
-
B.
hasLandmarkOnBank
Indicates that a landmark is located on the bank (shore or edge) of a geographic feature such as a river, lake, or canal.
-
C.
hasNotableSettlementRegion
Indicates that an entity has a significant or well-known settlement located within a specified geographic region.
-
D.
hasHumanSettlement
chosen
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
-
E.
hasProvinceOnBank
Indicates that a province is located along or adjacent to the bank of a specified 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_69ef52022538819081f873d0c84a6dd6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: April 27, 2026, 12:22 p.m.