Triple
T24742024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rs |
E618588
|
entity |
| Predicate | notISOStandardSymbol |
P126322
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Rs, notISOStandardSymbol, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notISOStandardSymbol Context triple: [Rs, notISOStandardSymbol, true]
-
A.
notOfficialISO4217SymbolFor
Indicates that a currency symbol or code is used informally or incorrectly and is not the official ISO 4217 symbol for that currency.
-
B.
notOfficialSymbolOf
Indicates that something is explicitly not recognized or designated as the official symbol of a given entity.
-
C.
notStandardizedBy
Indicates that an entity has not been brought into conformity with a particular standard, method, or specification by the referenced agent or authority.
-
D.
symbolIs
Indicates that one entity serves as the symbolic representation or sign of another entity.
-
E.
isNonISOCodeSymbol
chosen
Indicates that a symbol represents a code or notation that does not conform to any ISO standard coding system.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:17 a.m.