Triple
T10403947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barzakh as-Suways |
E245214
|
entity |
| Predicate | hasApproximateLengthNorthSouth |
P93720
|
FINISHED |
| Object | about 160 kilometers |
—
|
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: about 160 kilometers | Statement: [Barzakh as-Suways, hasApproximateLengthNorthSouth, about 160 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateLengthNorthSouth Context triple: [Barzakh as-Suways, hasApproximateLengthNorthSouth, about 160 kilometers]
-
A.
approximateLengthInMeters
Indicates the estimated or roughly measured length of something expressed in meters.
-
B.
hasApproximateDistanceFromEquator
Indicates that one entity has an approximate measured or estimated distance from the Earth's equator.
-
C.
navigableLengthApproxKm
Indicates the approximate distance, measured in kilometers, over which something (typically a waterway) can be navigated.
-
D.
approximateLengthInMiles
Indicates the estimated distance or extent of something measured in miles.
-
E.
hasCoastlineLengthApprox
Indicates an approximate measurement of the total length of an entity’s coastline.
- F. None of above. chosen
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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9e5fb58819081d7d3e1dc625197 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e944fac4819093b0312aa0efd729 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:08 p.m.