Triple
T25208655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dover Heights |
E631622
|
entity |
| Predicate | cadastralCounty |
P115787
|
FINISHED |
| Object | Cumberland County |
—
|
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: Cumberland County | Statement: [Dover Heights, cadastralCounty, Cumberland County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cadastralCounty Context triple: [Dover Heights, cadastralCounty, Cumberland County]
-
A.
isInCadastralCounty
chosen
Indicates that one entity is located within, and administratively belongs to, a specific cadastral county used for land and property registration.
-
B.
traditionalCountyIncludes
Indicates that a traditional or historic county geographically contains or encompasses another area or entity within its boundaries.
-
C.
primaryCountyOfParentMunicipality
Indicates that a given county is the main or principal county in which the parent municipality of an entity is located.
-
D.
governingCountyTown
Indicates that a county has governmental authority over, and is administratively responsible for, a particular town.
-
E.
adjacentToCounty
Indicates that one county directly borders or touches another county geographically.
- 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_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:57 p.m.