Triple
T4360969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan–Israel border |
E98658
|
entity |
| Predicate | demarcatedIn |
P519
|
FINISHED |
| Object | Israel–Jordan peace treaty annexes |
—
|
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: Israel–Jordan peace treaty annexes | Statement: [Jordan–Israel border, demarcatedIn, Israel–Jordan peace treaty annexes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demarcatedIn Context triple: [Jordan–Israel border, demarcatedIn, Israel–Jordan peace treaty annexes]
-
A.
demarcationType
Indicates the specific way in which a boundary or separation between entities is defined, marked, or categorized.
-
B.
dividedBetween
Indicates that something is partitioned or shared among two or more distinct entities or groups.
-
C.
defined
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
D.
marksBoundaryIn
Indicates that one entity serves as a boundary or delimiter within, or for a specific region or structure of, another entity.
-
E.
describedIn
chosen
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351e47d388190b31500189577cd75 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.