Triple
T20991879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Street |
E517044
|
entity |
| Predicate | hasRegionHighPointStatus |
P1674
|
FINISHED |
| Object | highest point of the Far Eastern Fells |
—
|
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: highest point of the Far Eastern Fells | Statement: [High Street, hasRegionHighPointStatus, highest point of the Far Eastern Fells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionHighPointStatus Context triple: [High Street, hasRegionHighPointStatus, highest point of the Far Eastern Fells]
-
A.
hasHighPointStatus
Indicates that an entity holds a high or elevated status within a point-based or ranking system.
-
B.
highestPointRegion
chosen
Indicates that one location is the highest point within a specified region.
-
C.
hasHighestPointType
Indicates that the highest point of an entity is of a specified type or category.
-
D.
highPointLocatedOn
Indicates that the highest point of one entity is situated on or atop another entity.
-
E.
regionTallestStatus
Indicates that an entity holds the status of being the tallest within a specified region.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc1cbb10819089e4f1445b921946 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:50 p.m.