Triple
T32240700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Jaghbub |
E823603
|
entity |
| Predicate | distanceToMediterraneanCoastApprox |
P16475
|
FINISHED |
| Object | 250 km |
—
|
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: 250 km | Statement: [Al-Jaghbub, distanceToMediterraneanCoastApprox, 250 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMediterraneanCoastApprox Context triple: [Al-Jaghbub, distanceToMediterraneanCoastApprox, 250 km]
-
A.
distanceFromMediterranean
chosen
Indicates the measured spatial distance between a given location and the Mediterranean Sea.
-
B.
distanceToTurkishCoast
Indicates the measured or calculated spatial distance between a given location or object and the coastline of Turkey.
-
C.
borderDirectionRelativeToMediterraneanSea
Indicates the directional orientation of an entity’s border in relation to the Mediterranean Sea (e.g., whether it borders the sea to the north, south, east, or west).
-
D.
dateToReachMediterranean
Indicates the date on which an entity is expected or scheduled to arrive at, or first reach, the Mediterranean.
-
E.
distanceFromCoast
Indicates the measured spatial separation between a location and the nearest point on a coastline.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0346b487088190814e4bd0765cb609 |
completed | May 12, 2026, 3:26 p.m. |
| PD | Predicate disambiguation | batch_6a0346428c60819090e5ea815c0921ca |
completed | May 12, 2026, 3:24 p.m. |
Created at: May 1, 2026, 12:40 a.m.