Triple
T36243403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chollerford |
E891588
|
entity |
| Predicate | locatedInNationalTrailArea |
P204803
|
FINISHED |
| Object | Hadrian’s Wall Path |
E194619
|
NE 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: Hadrian’s Wall Path | Statement: [Chollerford, locatedInNationalTrailArea, Hadrian’s Wall Path]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInNationalTrailArea Context triple: [Chollerford, locatedInNationalTrailArea, Hadrian’s Wall Path]
-
A.
locatedInNationalParkOrQuasiNationalPark
Indicates that something is situated within the boundaries of a national park or a quasi-national park.
-
B.
locatedInNationalOrProvincialPark
Indicates that one entity is situated within the boundaries of a national or provincial park.
-
C.
locatedWithinNationalLandscape
Indicates that one entity is geographically situated inside the boundaries of a designated national landscape area.
-
D.
locatedInNationalCharacterArea
Indicates that one entity is geographically situated within the boundaries of a specified national character area.
-
E.
locatedNearNationalPark
Indicates that one place or entity is situated in close proximity to a national park.
- F. None of above. chosen
Provenance (5 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_69f76e44993481908fa75e4c48d0aab3 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a394d44a18c8190a2ff3b6b06a86a4f |
completed | June 22, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:09 p.m.