Triple
T15297638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cannop Ponds |
E365699
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Parkend |
E365914
|
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: Parkend | Statement: [Cannop Ponds, near, Parkend]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Parkend Context triple: [Cannop Ponds, near, Parkend]
-
A.
Parkend
chosen
Parkend is a small village situated within England’s historic Forest of Dean, known for its woodland surroundings and industrial heritage.
-
B.
Parkring
Parkring is a central boulevard in Vienna that forms part of the historic Ringstrasse, known for its grand architecture and proximity to prominent parks and landmarks.
-
C.
Parkar
Parkar is a less common spelling variant of the surname Parker, which is of English origin.
-
D.
Ottopark
Ottopark is a small urban green space in Berlin’s Moabit district, offering residents a local spot for relaxation and recreation.
-
E.
Ketetahi car park
Ketetahi car park is a main access point and parking area for hikers using the Ketetahi end of New Zealand’s Tongariro Alpine Crossing.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03686bfb8819080ba0caae652170a |
completed | April 16, 2026, 1:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feef82f6d08190b809260dda247dfe |
completed | May 9, 2026, 8:25 a.m. |
Created at: April 10, 2026, 3:15 a.m.