Triple
T27654956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garden Parish |
E696968
|
entity |
| Predicate | associatedWithParishCapital |
P42007
|
FINISHED |
| Object | St. Ann's Bay |
—
|
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: St. Ann's Bay | Statement: [Garden Parish, associatedWithParishCapital, St. Ann's Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithParishCapital Context triple: [Garden Parish, associatedWithParishCapital, St. Ann's Bay]
-
A.
mainParishOf
Indicates that one parish serves as the primary or central parish associated with a given entity or area.
-
B.
associatedWithCountySeat
Indicates that an entity has a relationship or connection to a county’s administrative center or county seat.
-
C.
isParishSeatOf
chosen
Indicates that a location serves as the administrative center or main seat of government for a particular parish.
-
D.
civilParishGroupedWith
Indicates that two or more civil parishes are administratively associated or treated as a single grouped unit for certain official or organizational purposes.
-
E.
parishWith
Indicates that one entity is associated with, belongs to, or is administered together with another entity as part of the same parish.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a003ffb548081908ba64fd2b570f42f |
completed | May 10, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_6a003fcecf788190a13dff38b9de3414 |
completed | May 10, 2026, 8:20 a.m. |
Created at: April 27, 2026, 2:33 p.m.