Triple
T33073210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hairatan |
E846289
|
entity |
| Predicate | locatedOnBorderFeature |
P195186
|
FINISHED |
| Object | Amu Darya River |
E43947
|
NE FINISHED |
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: Amu Darya River | Statement: [Hairatan, locatedOnBorderFeature, Amu Darya River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnBorderFeature Context triple: [Hairatan, locatedOnBorderFeature, Amu Darya River]
-
A.
liesOnBorderOf
Indicates that one entity is located along or directly adjacent to the boundary line separating it from another entity.
-
B.
regionBorderFeature
chosen
Indicates that a region’s boundary is defined, marked, or characterized by a particular geographic feature.
-
C.
nearInternationalBoundary
Indicates that one entity is located close to an international boundary separating two or more countries.
-
D.
locatedNearStateBorderWith
Indicates that one entity is situated geographically close to the border of a specified state.
-
E.
connectsToCountryBorder
Indicates that one entity is directly adjacent to and touches the border of a specified country.
- F. None of above.
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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a03544239d4819087b6c232d6804977 |
completed | May 12, 2026, 4:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a352fa8fb0c8190b6a87d714dda65f4 |
completed | June 19, 2026, 12:01 p.m. |
| PD | Predicate disambiguation | batch_6a0353d685688190b01df77fc2f62bf2 |
completed | May 12, 2026, 4:22 p.m. |
Created at: May 1, 2026, 1:25 a.m.