Triple
T35039506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Bolton Lake |
E1011027
|
entity |
| Predicate | isMiddleOf |
P134498
|
FINISHED |
| Object | three-lake Bolton chain |
—
|
NE NERFINISHED |
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: three-lake Bolton chain | Statement: [Middle Bolton Lake, isMiddleOf, three-lake Bolton chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMiddleOf Context triple: [Middle Bolton Lake, isMiddleOf, three-lake Bolton chain]
-
A.
hasMiddleLetter
Indicates that one entity is the character (or sequence) that appears in the middle position of another entity’s string or word.
-
B.
isIntermediateBetween
Indicates that one entity occupies a position or state that lies between two other entities in a sequence, range, or process.
-
C.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
-
D.
midpoint
chosen
Indicates that one entity is the exact center point lying halfway between two other entities in space or along a segment.
-
E.
isMidterm
Indicates that an event, exam, or assessment occurs in the middle portion of an academic term or course.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7859072cc8190b4801985dacff7e8 |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.