Triple
T8932266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L$ |
E212684
|
entity |
| Predicate | ISO4217CodeOfCurrency |
P86254
|
FINISHED |
| Object | LRD |
—
|
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: LRD | Statement: [L$, ISO4217CodeOfCurrency, LRD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO4217CodeOfCurrency Context triple: [L$, ISO4217CodeOfCurrency, LRD]
-
A.
ISO4217Currency
Indicates that an entity is a currency defined and standardized under the ISO 4217 international currency code system.
-
B.
ISO4217Section
Indicates that something is associated with, defined in, or categorized under a specific section of the ISO 4217 currency standard.
-
C.
ISO4217CurrencyManaged
Indicates that an entity is responsible for administering, regulating, or overseeing a specific ISO 4217 currency.
-
D.
ISO4217Category
Indicates the classification or type category assigned to a currency according to the ISO 4217 standard.
-
E.
ISO4217CurrencyCodeIssued
Indicates that a specific ISO 4217 currency code has been officially issued or assigned as a valid currency identifier.
- F. None of above. chosen
Provenance (4 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc668e5c108190b08f9cd6b4fd4a8b |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc608331f88190bcb500ff63527f8a |
completed | April 1, 2026, 12:02 a.m. |
Created at: March 30, 2026, 6:57 p.m.