Triple
T26645188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isthmus of Kra region |
E668887
|
entity |
| Predicate | approximateMinimumWidthInMiles |
P180208
|
FINISHED |
| Object | 27 |
—
|
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: 27 | Statement: [Isthmus of Kra region, approximateMinimumWidthInMiles, 27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateMinimumWidthInMiles Context triple: [Isthmus of Kra region, approximateMinimumWidthInMiles, 27]
-
A.
approximateLengthInMiles
Indicates the estimated distance or extent of something measured in miles.
-
B.
typicalRangeMinimum_km
Indicates the minimum distance, in kilometers, that is typically observed or expected within a given range for the relationship or measurement in question.
-
C.
navigableLengthApproxKm
Indicates the approximate distance, measured in kilometers, over which something (typically a waterway) can be navigated.
-
D.
riverMileRange
Indicates a relationship specifying that something occurs, applies, or is located between two given mile markers along a river.
-
E.
trackLengthMiles
Indicates the length of a track measured in miles.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
| PDg | Predicate description generation | batch_69f739a58b3c81908abc2b8738a65678 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 27, 2026, 2:31 a.m.