Triple
T5653942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitworth |
E124570
|
entity |
| Predicate | lieWithin |
P32883
|
FINISHED |
| Object | Pennines foothills |
—
|
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: Pennines foothills | Statement: [Whitworth, lieWithin, Pennines foothills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lieWithin Context triple: [Whitworth, lieWithin, Pennines foothills]
-
A.
liesOutside
Indicates that one entity is located entirely beyond the spatial or conceptual boundary of another entity.
-
B.
liesIn
chosen
Indicates that one entity is located within the spatial, geographical, or conceptual boundaries of another entity.
-
C.
existsWithin
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
-
D.
liesBelow
Indicates that one entity is positioned at a lower vertical level than another entity.
-
E.
liesWithinLatitudeBand
Indicates that one geographic entity is located within a specified range of latitudes defined as a latitude band.
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022f7efec8190946c925130176d5a |
completed | March 22, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69c01b2274b48190b2ef57ed728f785c |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:42 p.m.