Triple
T7598408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnley Embankment |
E179917
|
entity |
| Predicate | elevatesAbove |
P31686
|
FINISHED |
| Object | town of Burnley |
—
|
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: town of Burnley | Statement: [Burnley Embankment, elevatesAbove, town of Burnley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatesAbove Context triple: [Burnley Embankment, elevatesAbove, town of Burnley]
-
A.
elevatedTo
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
B.
elevatedFeature
chosen
Indicates that one feature or element is positioned or raised higher relative to another reference level or surrounding context.
-
C.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
D.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
E.
heightAboveSurroundings
Indicates that an entity’s vertical position or elevation is higher than that of its immediate surrounding area.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d67cf88190a3202c07f7cea7df |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.