Triple
T33824560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirkou |
E866923
|
entity |
| Predicate | locatedInCountryBorderRegionWith |
P126842
|
FINISHED |
| Object | Libya |
E1495
|
NE 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: Libya | Statement: [Dirkou, locatedInCountryBorderRegionWith, Libya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCountryBorderRegionWith Context triple: [Dirkou, locatedInCountryBorderRegionWith, Libya]
-
A.
connectsToCountryBorder
chosen
Indicates that one entity is directly adjacent to and touches the border of a specified country.
-
B.
locatedNearStateBorderWith
Indicates that one entity is situated geographically close to the border of a specified state.
-
C.
isInNationalBorderRegion
Indicates that one entity is located within the national border region or boundary area of another entity.
-
D.
hasBorderWithinCountry
Indicates that one region or area shares an internal boundary with another region or area within the same country.
-
E.
hasCountryBorderWith
Indicates that two countries share a common land or maritime boundary.
- F. None of above.
Provenance (4 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36760d7218819086b6f64357b5a4b9 |
completed | June 20, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:46 a.m.