Triple
T29730643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Alexandropol |
E752309
|
entity |
| Predicate | fixedBorderBetween |
P122826
|
FINISHED |
| Object | Turkey and Armenia |
—
|
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: Turkey and Armenia | Statement: [Treaty of Alexandropol, fixedBorderBetween, Turkey and Armenia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fixedBorderBetween Context triple: [Treaty of Alexandropol, fixedBorderBetween, Turkey and Armenia]
-
A.
adjustedBorderBetween
Indicates that the boundary separating two entities has been modified or realigned from its previous position.
-
B.
guaranteedBorderBetween
Indicates a formally assured and recognized boundary relationship that definitively separates two regions or entities.
-
C.
borderDefinedBetween
chosen
Indicates that a boundary line or border is formally established between two geographic or political entities.
-
D.
guardedBorderWith
Indicates a relationship where a shared border between two entities is actively protected or monitored, typically for security or control purposes.
-
E.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6732fff7c81908326c2deaffcdf86 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:42 p.m.