Triple
T32092050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wantsum Channel system |
E819620
|
entity |
| Predicate | widthHistorical |
P173526
|
FINISHED |
| Object | up to about 2 miles |
—
|
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: up to about 2 miles | Statement: [Wantsum Channel system, widthHistorical, up to about 2 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widthHistorical Context triple: [Wantsum Channel system, widthHistorical, up to about 2 miles]
-
A.
historicalLength
Indicates the duration or extent of time over which something has existed, occurred, or been recorded in the past.
-
B.
historicalSpread
Indicates how something has expanded, diffused, or propagated across time and/or space throughout history.
-
C.
historicalRange
Indicates the time period over which something existed, was active, or was relevant in history.
-
D.
historicalType
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
-
E.
historicalLevel
Indicates the degree or extent to which something is related to, situated in, or characterized by a particular historical period or context.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b63edd4c819093b664b38a69d7c8 |
completed | May 3, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:25 a.m.