Triple
T29036208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caribbean guilder |
E737864
|
entity |
| Predicate | plannedIntroductionRegion |
P173724
|
FINISHED |
| Object | Dutch Caribbean |
—
|
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: Dutch Caribbean | Statement: [Caribbean guilder, plannedIntroductionRegion, Dutch Caribbean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedIntroductionRegion Context triple: [Caribbean guilder, plannedIntroductionRegion, Dutch Caribbean]
-
A.
regionTypePlanned
Indicates that a region is intended or designated to have a specific type or classification in a planned or future state.
-
B.
partOfPlanningRegion
Indicates that one entity is included within, or belongs to, a larger designated planning region.
-
C.
proposedForRegion
chosen
Indicates that something has been suggested or designated to apply to, operate in, or be associated with a particular geographic or administrative region.
-
D.
plannedArea
Indicates that an area is designated or intended for a specific planned use or development.
-
E.
exportRegion
Indicates the region or geographic area from which goods, services, or resources are exported.
- 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 9:58 a.m.