Triple
T19177244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porlock |
E469470
|
entity |
| Predicate | parishIncludes |
P38128
|
FINISHED |
| Object | Porlock Weir |
—
|
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: Porlock Weir | Statement: [Porlock, parishIncludes, Porlock Weir]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Porlock Weir Context triple: [Porlock, parishIncludes, Porlock Weir]
-
A.
Porlock Weir
chosen
Porlock Weir is a small historic harbour hamlet on the coast of Somerset, England, known for its picturesque thatched cottages, pebble beach, and tidal harbour.
-
B.
Shepperton Weir
Shepperton Weir is a Thames River weir in Surrey, England, that helps control water levels and flow near Shepperton Lock.
-
C.
Tottenham Lock
Tottenham Lock is a canal lock on the River Lea in North London, used to manage water levels and enable boat navigation along the river.
-
D.
Nuneham Lock
Nuneham Lock is a lock on the River Thames in Oxfordshire, England, serving river traffic near the village of Nuneham Courtenay.
-
E.
Porlock Hill
Porlock Hill is a famously steep and winding road in Somerset, England, known as one of the country’s most challenging and scenic driving climbs.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f618f18c8190b98995fda4b6fea0 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 10, 2026, 12:07 p.m.