Triple
T27273418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pye Bridge |
E688118
|
entity |
| Predicate | partOfLocalArea |
P136203
|
FINISHED |
| Object | Amber Valley district |
—
|
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: Amber Valley district | Statement: [Pye Bridge, partOfLocalArea, Amber Valley district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfLocalArea Context triple: [Pye Bridge, partOfLocalArea, Amber Valley district]
-
A.
neighborhood
Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
-
B.
partOfNeighborhoodNetwork
Indicates that an entity belongs to, or is included within, a specific neighborhood’s interconnected network or system.
-
C.
residesNear
Indicates that one entity lives or is located in close physical proximity to another entity.
-
D.
regionOfTown
chosen
Indicates that one entity is a specific area or district that forms part of a town.
-
E.
partlyInAdministrativeArea
Indicates that an entity is located such that only a portion of it lies within a specified administrative area (e.g., a city, county, or 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 27, 2026, 11:01 a.m.