Triple
T29465999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | as-Safa region |
E747380
|
entity |
| Predicate | modernCountryBorderCrossed |
P30010
|
FINISHED |
| Object | Syria–Jordan border |
—
|
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: Syria–Jordan border | Statement: [as-Safa region, modernCountryBorderCrossed, Syria–Jordan border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernCountryBorderCrossed Context triple: [as-Safa region, modernCountryBorderCrossed, Syria–Jordan border]
-
A.
sharesInternationalBorderWith
chosen
Indicates that two geographic or political entities have a common boundary that is recognized as an international border.
-
B.
crossBorderPeople
Indicates the movement or presence of people across national or regional borders.
-
C.
EUInternalBorder
Indicates that a border lies between two member states within the European Union, where internal EU border rules apply.
-
D.
nearestInternationalBorderCrossingCountry
Indicates the country in which the closest international border crossing point to a given location is situated.
-
E.
borderTownAcrossBorder
Indicates that a town lies on one side of a border directly opposite or adjacent to a town on the other side of that border.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 28, 2026, 3:53 p.m.