Triple
T2738019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anguilla |
E60676
|
entity |
| Predicate | currencyCode |
P208
|
FINISHED |
| Object | XCD |
E71603
|
NE 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: XCD | Statement: [Anguilla, currencyCode, XCD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XCD Context triple: [Anguilla, currencyCode, XCD]
-
A.
XCD
chosen
XCD is the ISO 4217 currency code for the Eastern Caribbean dollar, the official monetary unit used by several Eastern Caribbean nations.
-
B.
XDS
XDS (Cross-Enterprise Document Sharing) is an IHE IT Infrastructure profile that defines standards-based methods for registering, storing, and sharing clinical documents across healthcare enterprises.
-
C.
CX
CX is the two-letter IATA airline designator used to identify Cathay Pacific in global aviation systems.
-
D.
XCA
XCA (Cross-Community Access) is an IHE IT Infrastructure profile that enables the discovery and retrieval of patient health records across different healthcare communities or domains.
-
E.
XHP
XHP is the IATA station code assigned to Paris's Gare de l'Est railway station.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb147a588190829b74fe05b3a114 |
completed | March 7, 2026, 8 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afbbc607d88190bc35ce56ac26dbf9 |
completed | March 10, 2026, 6:35 a.m. |
Created at: March 6, 2026, 9:56 p.m.