Triple
T22986303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan and Syria |
E571615
|
entity |
| Predicate | borderCreatedFrom |
P14046
|
FINISHED |
| Object | post–World War I colonial boundaries |
—
|
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: post–World War I colonial boundaries | Statement: [Jordan and Syria, borderCreatedFrom, post–World War I colonial boundaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCreatedFrom Context triple: [Jordan and Syria, borderCreatedFrom, post–World War I colonial boundaries]
-
A.
borderEstablished
Indicates that a formal boundary between two geographic or political entities has been officially defined and put into effect.
-
B.
borderDefinedBy
chosen
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
-
C.
borderChange
Indicates a change in the boundaries between geographic or political entities, such as when borders are redrawn, expanded, reduced, or otherwise altered over time.
-
D.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
E.
borderSectionOf
Indicates that one entity represents a specific segment or portion of the overall border of 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182996ee08190ab74014ee7ecac2b |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:49 p.m.