Triple
T37065849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amesbury Community Area |
E917440
|
entity |
| Predicate | hasParishOrTownCouncil |
P21036
|
FINISHED |
| Object | Amesbury Town Council |
—
|
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: Amesbury Town Council | Statement: [Amesbury Community Area, hasParishOrTownCouncil, Amesbury Town Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishOrTownCouncil Context triple: [Amesbury Community Area, hasParishOrTownCouncil, Amesbury Town Council]
-
A.
hasParishCouncils
chosen
Indicates that an entity possesses, is served by, or is administratively associated with one or more parish councils.
-
B.
hasCivilParishComponent
Indicates that an entity includes or is composed of the specified civil parish as one of its administrative components.
-
C.
hasCountyCouncil
Indicates that an entity is administratively governed or overseen by a specific county council.
-
D.
hasCivilParishStatus
Indicates that an entity holds the official administrative status or designation of a civil parish.
-
E.
civilParishCouncil
Indicates that a civil parish is governed or administered by a particular parish council.
- F. None of above.
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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00383e868c819098fd17e25fcbdb04 |
completed | May 10, 2026, 7:48 a.m. |
| PD | Predicate disambiguation | batch_6a0037cc59688190b7b9da939a413db3 |
completed | May 10, 2026, 7:46 a.m. |
Created at: May 3, 2026, 4:14 p.m.