Triple
T14280654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portuguese real |
E354035
|
entity |
| Predicate | ISO4217LikeStatus |
P86101
|
FINISHED |
| Object | existed before modern ISO codes |
—
|
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: existed before modern ISO codes | Statement: [Portuguese real, ISO4217LikeStatus, existed before modern ISO codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO4217LikeStatus Context triple: [Portuguese real, ISO4217LikeStatus, existed before modern ISO codes]
-
A.
ISO4217Category
Indicates the classification or type category assigned to a currency according to the ISO 4217 standard.
-
B.
ISO4217CurrencyManaged
Indicates that an entity is responsible for administering, regulating, or overseeing a specific ISO 4217 currency.
-
C.
hasISO4217Status
chosen
Indicates the classification or status of a currency according to the ISO 4217 standard.
-
D.
ISO4217Currency
Indicates that an entity is a currency defined and standardized under the ISO 4217 international currency code system.
-
E.
ISO4217Section
Indicates that something is associated with, defined in, or categorized under a specific section of the ISO 4217 currency standard.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de697b5e8081908e5b91a3a1c55df9 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.