Triple
T34655617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GGT |
E889965
|
entity |
| Predicate | servesPrimarySettlement |
P13187
|
FINISHED |
| Object | George Town, Great Exuma |
—
|
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: George Town, Great Exuma | Statement: [GGT, servesPrimarySettlement, George Town, Great Exuma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesPrimarySettlement Context triple: [GGT, servesPrimarySettlement, George Town, Great Exuma]
-
A.
servesSettlement
Indicates that one entity provides services or support to a particular settlement or community.
-
B.
hasPrimarySettlementFunction
Indicates that a settlement’s main or dominant functional role (e.g., residential, commercial, industrial, administrative) is of the specified type.
-
C.
servedSettlementType
Indicates the type of settlement (e.g., city, town, village) that is provided service or coverage by a given entity.
-
D.
mainSettlement
chosen
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
E.
accessToPrimarySettlement
Indicates that an entity has the ability or right to reach, use, or benefit from a designated primary settlement.
- 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffc7b4c7f88190b6357a44e7f0940f |
completed | May 9, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69ffc755f09c8190995ca00d97336988 |
completed | May 9, 2026, 11:46 p.m. |
Created at: May 1, 2026, 2:04 a.m.