Triple
T34655529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pig Beach |
E889963
|
entity |
| Predicate | currencyUsedInRegion |
P18115
|
FINISHED |
| Object | Bahamian dollar |
—
|
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: Bahamian dollar | Statement: [Pig Beach, currencyUsedInRegion, Bahamian dollar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyUsedInRegion Context triple: [Pig Beach, currencyUsedInRegion, Bahamian dollar]
-
A.
currencyCountry
Indicates that a given currency is officially used as legal tender in a particular country.
-
B.
currencyUsedFor
Indicates that a particular currency is used as the medium of exchange or legal tender for a given entity, such as a country, region, or organization.
-
C.
currencyArea
chosen
Indicates that one entity is the geographic or economic region in which the other entity’s currency is officially used or valid.
-
D.
localCurrency
Indicates that a particular currency is officially used or recognized as the standard medium of exchange within a specific locality, region, or country.
-
E.
currencySignAdopted
Indicates that a particular currency sign has been officially adopted for use with a given currency or monetary system.
- 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_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: May 1, 2026, 2:04 a.m.