Triple
T532977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morant Bay |
E12263
|
entity |
| Predicate | hasPostalRole |
P16524
|
FINISHED |
| Object | postal town for Saint Thomas Parish |
—
|
LITERAL FINISHED |
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: postal town for Saint Thomas Parish | Statement: [Morant Bay, hasPostalRole, postal town for Saint Thomas Parish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostalRole Context triple: [Morant Bay, hasPostalRole, postal town for Saint Thomas Parish]
-
A.
hasPostalSystem
Indicates that an entity possesses or operates an organized system for sending, receiving, and delivering mail or parcels.
-
B.
postalService
Indicates a relationship where one entity provides or manages the delivery and handling of mail and packages for another entity.
-
C.
hasPostalCodePrefix
Indicates that a location’s postal code begins with a specified sequence of characters.
-
D.
postalCode
Indicates the numerical or alphanumerical code assigned to a geographic area for mail delivery associated with an entity.
-
E.
hasPostalAbbreviationState
Indicates that a state is associated with a specific standardized postal abbreviation.
- F. None of above. chosen
Provenance (4 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b3e49081909810fa417b31306f |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49857e1148190aa782b82675cf0b5 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.