Triple
T15993018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reed |
E387884
|
entity |
| Predicate | civilParish |
P2739
|
FINISHED |
| Object | Reed |
E387884
|
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: Reed | Statement: [Reed, civilParish, Reed]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Reed Context triple: [Reed, civilParish, Reed]
-
A.
Reed
Reed is a given name and surname of English and Scottish origin, commonly associated with meanings related to red hair or a person living near reeds.
-
B.
Reed
chosen
Reed is a small rural village located within the North Hertfordshire district of Hertfordshire, England.
-
C.
Reeth
Reeth is a picturesque village in North Yorkshire, England, known as a popular walking and cycling base in Swaledale within the Yorkshire Dales National Park.
-
D.
Ryen
Ryen is a residential neighborhood in Oslo, Norway, known for its apartment blocks, local amenities, and good public transport connections.
-
E.
Rhees
Rhees is a surname of Welsh origin borne by various notable individuals in fields such as philosophy, education, and public service.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e15785347081908831b4cbc9a2dd45 |
completed | April 16, 2026, 9:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffc3d3ef2881909213ff608192f1ef |
completed | May 9, 2026, 11:31 p.m. |
Created at: April 10, 2026, 4:54 a.m.