Triple
T29036205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caribbean guilder |
E737864
|
entity |
| Predicate | isoCodeStatus |
P78768
|
FINISHED |
| Object | not yet assigned |
—
|
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: not yet assigned | Statement: [Caribbean guilder, isoCodeStatus, not yet assigned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isoCodeStatus Context triple: [Caribbean guilder, isoCodeStatus, not yet assigned]
-
A.
isoStatus
Indicates the ISO (International Organization for Standardization) compliance or certification status associated with an entity or process.
-
B.
ISOCode
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
-
C.
ISO3166Status
chosen
Indicates the classification or current standing of an entity under the ISO 3166 country code standard (e.g., official, reserved, or deleted status).
-
D.
ISOCodeContext
Indicates the contextual framework or domain within which a particular ISO code is defined, interpreted, or applied.
-
E.
hasISOCode
Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
- 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_69f6603db2988190af8ce0beaaec257d |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:58 a.m.