Triple
T31513582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algeria–Tunisia border |
E804007
|
entity |
| Predicate | hasNorthernEnd |
P15231
|
FINISHED |
| Object | near Mediterranean coast |
—
|
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: near Mediterranean coast | Statement: [Algeria–Tunisia border, hasNorthernEnd, near Mediterranean coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNorthernEnd Context triple: [Algeria–Tunisia border, hasNorthernEnd, near Mediterranean coast]
-
A.
locatedAtNorthernEndOf
chosen
Indicates that one entity is situated at or near the northernmost part or extremity of another entity.
-
B.
northernTerminusVariant
Indicates that one location or feature serves as an alternative or variant northern endpoint of a route, line, or path.
-
C.
isNorthernmost
Indicates that one entity is located farther north than all other comparable entities in a given set or region.
-
D.
northernTerminusConnects
Indicates that a route, line, or pathway connects to or ends at a specified location at its northernmost terminus.
-
E.
northernTerminusRegion
Indicates that a location or route has its northern endpoint or final stopping point within a specified region.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00a846a8f881908b073ad13a5af6ca |
completed | May 10, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_6a00a7aae194819085e1a2fd406f7922 |
completed | May 10, 2026, 3:43 p.m. |
Created at: April 30, 2026, 9:51 p.m.