Triple
T22361322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayfield Parish Council |
E552784
|
entity |
| Predicate | governs |
P760
|
FINISHED |
| Object | Mayfield |
—
|
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: Mayfield | Statement: [Mayfield Parish Council, governs, Mayfield]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mayfield Context triple: [Mayfield Parish Council, governs, Mayfield]
-
A.
Mayfield
Mayfield is a residential suburb on the north side of Cork City in Ireland, known for its local community amenities and proximity to the city centre.
-
B.
Mayfield
Mayfield is a residential suburb located within the city of Newcastle in New South Wales, Australia.
-
C.
Mayfield
Mayfield is a village in Midlothian, Scotland, situated near Dalkeith and primarily known as a residential community with local amenities serving the surrounding area.
-
D.
Mayfield
chosen
Mayfield is a village and civil parish in East Sussex, England, known for its historic High Street and traditional English countryside setting.
-
E.
Mayfield
Mayfield is a residential district within the London Borough of Redbridge in northeast London.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157d44a908190b16e4cfdf4591b10 |
completed | April 29, 2026, 12:59 a.m. |
Created at: April 16, 2026, 8:44 p.m.