Triple
T30921468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rouvroy |
E787735
|
entity |
| Predicate | hasBorderSettlement |
P46520
|
FINISHED |
| Object | Torgny |
—
|
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: Torgny | Statement: [Rouvroy, hasBorderSettlement, Torgny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderSettlement Context triple: [Rouvroy, hasBorderSettlement, Torgny]
-
A.
borderSettlement
chosen
Indicates that a settlement is located near or along a political or administrative border.
-
B.
hasBorderCity
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
C.
hasBorderWithinCountry
Indicates that one region or area shares an internal boundary with another region or area within the same country.
-
D.
hasBorderTownRole
Indicates that an entity serves in an official capacity or role specifically related to a town located on or near a border.
-
E.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 29, 2026, 8:51 p.m.