Triple
T14901399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rafahi |
E360011
|
entity |
| Predicate | associatedWithBorder |
P37800
|
FINISHED |
| Object | Egypt–Gaza border |
—
|
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: Egypt–Gaza border | Statement: [Rafahi, associatedWithBorder, Egypt–Gaza border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithBorder Context triple: [Rafahi, associatedWithBorder, Egypt–Gaza border]
-
A.
relatedBorder
Indicates that two geographic or political entities share a common boundary or border with each other.
-
B.
hasBorderRelation
chosen
Indicates that one entity shares a boundary or border with another entity.
-
C.
associatedWithFront
Indicates a relationship where one entity is linked or connected specifically to the front part, side, or face of another entity.
-
D.
hasBorderThrough
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
E.
usedAsBorder
Indicates that one entity functions as a boundary or dividing line for 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded609bf68819099ca3aa3fe1acadc |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:11 a.m.