Triple
T25325044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amda Seyon I |
E634987
|
entity |
| Predicate | strengthenedBorder |
P144415
|
FINISHED |
| Object | frontiers with Muslim states to the east and southeast |
—
|
LITERAL 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: frontiers with Muslim states to the east and southeast | Statement: [Amda Seyon I, strengthenedBorder, frontiers with Muslim states to the east and southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthenedBorder Context triple: [Amda Seyon I, strengthenedBorder, frontiers with Muslim states to the east and southeast]
-
A.
guardedBorderWith
chosen
Indicates a relationship where a shared border between two entities is actively protected or monitored, typically for security or control purposes.
-
B.
sharesBorderType
Indicates that two entities are connected by a common boundary characterized by the same specified type of border (e.g., land, river, maritime).
-
C.
relatedBorder
Indicates that two geographic or political entities share a common boundary or border with each other.
-
D.
borderColor
Indicates the color that forms the boundary or outline of an entity.
-
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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f496928630819090e20713e47fb324 |
completed | May 1, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:30 p.m.