Triple
T33120664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saudi Arabia–Yemen border area |
E847586
|
entity |
| Predicate | borderDefinedByTreaty |
P14046
|
FINISHED |
| Object | Treaty of Taif |
—
|
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: Treaty of Taif | Statement: [Saudi Arabia–Yemen border area, borderDefinedByTreaty, Treaty of Taif]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDefinedByTreaty Context triple: [Saudi Arabia–Yemen border area, borderDefinedByTreaty, Treaty of Taif]
-
A.
borderDemarcationTreaties
Indicates the existence of formal treaties that define, establish, or adjust the official boundary lines between two or more territories or jurisdictions.
-
B.
borderTreatySignedOn
Indicates that a formal agreement establishing or modifying a border between entities was signed on a specific date.
-
C.
borderWithTerritory
Indicates that one territory shares a common boundary or border with another territory.
-
D.
borderDefinedBy
chosen
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
-
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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 1, 2026, 1:27 a.m.