Triple
T26309602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian Mediterranean Fleet |
E661784
|
entity |
| Predicate | countryBorderProtected |
P40726
|
FINISHED |
| Object | northern maritime border of Egypt |
—
|
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: northern maritime border of Egypt | Statement: [Egyptian Mediterranean Fleet, countryBorderProtected, northern maritime border of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryBorderProtected Context triple: [Egyptian Mediterranean Fleet, countryBorderProtected, northern maritime border of Egypt]
-
A.
countyBorder
Indicates that two counties share a common boundary or border with each other.
-
B.
countryBorderType
Indicates the type or nature of the border relationship that exists between two countries.
-
C.
countryBorderFeatureOf
chosen
Indicates that a geographical feature (such as a river, mountain range, or coastline) serves as or is part of the border of a country.
-
D.
countryBorderFunction
Indicates that one country shares a land or maritime boundary with another country.
-
E.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 26, 2026, 10:21 p.m.