Triple
T25208656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dover Heights |
E631622
|
entity |
| Predicate | cadastralParish |
P78401
|
FINISHED |
| Object | Parish of Alexandria |
—
|
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: Parish of Alexandria | Statement: [Dover Heights, cadastralParish, Parish of Alexandria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cadastralParish Context triple: [Dover Heights, cadastralParish, Parish of Alexandria]
-
A.
civilParishIn
Indicates that a civil parish is located within or administratively belongs to a specified larger geographic or governmental area.
-
B.
civilParishNumber
Indicates the identifying number assigned to a specific civil parish within an administrative or geographic system.
-
C.
civilParishFor
chosen
Indicates that one entity is the civil parish to which another entity (such as a place or administrative area) belongs or is assigned.
-
D.
civilParishArea
Indicates the total geographic area encompassed by a given civil parish.
-
E.
onlyCivilParishOf
Indicates that one entity is the sole civil parish associated with, or contained within, the other entity, with no other civil parishes sharing that association.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f474bda9288190947d325fe514571d |
completed | May 1, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:57 p.m.