Triple
T31771364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Akhal |
E810945
|
entity |
| Predicate | delimitedFrontierBetween |
P122826
|
FINISHED |
| Object | Persian Khorasan |
—
|
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: Persian Khorasan | Statement: [Treaty of Akhal, delimitedFrontierBetween, Persian Khorasan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: delimitedFrontierBetween Context triple: [Treaty of Akhal, delimitedFrontierBetween, Persian Khorasan]
-
A.
wasDemarcatedBetween
Indicates that a boundary or dividing line was formally established separating one entity from another.
-
B.
frontierWith
Indicates that two regions or territories share a common boundary or border, especially one marking the edge of settled or controlled area.
-
C.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
D.
borderDefinedBetween
chosen
Indicates that a boundary line or border is formally established between two geographic or political entities.
-
E.
frontLineBetween
Indicates that a boundary or line of direct confrontation exists separating two opposing sides or regions.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaff7648190a488163179a28fc2 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:33 p.m.