Triple
T892898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibraltar pound |
E19279
|
entity |
| Predicate | circulatesAsCash |
P8016
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gibraltar pound, circulatesAsCash, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circulatesAsCash Context triple: [Gibraltar pound, circulatesAsCash, yes]
-
A.
circulatedAs
Indicates that something was distributed, shared, or passed around in the form or role specified by the related entity.
-
B.
hasCashForm
chosen
Indicates that something exists or is available specifically in the form of cash.
-
C.
isLegalTenderFor
Indicates that a particular currency or form of money is officially recognized by a governing authority as valid payment for debts and financial transactions within a specified jurisdiction.
-
D.
demonetized
Indicates that something has lost its status or validity as legal tender or a source of monetization, and can no longer be used to generate revenue in the usual way.
-
E.
usedByDenomination
Indicates that something (such as an object, practice, or concept) is employed or utilized by a particular religious denomination.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad0304b081908d4c92bb2beadb81 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9372e88190b5a9db4afdc045c6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.