Triple
T8644871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanian leu |
E204748
|
entity |
| Predicate | ISO4217Code |
P189
|
FINISHED |
| Object | RON |
E246092
|
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: RON | Statement: [Romanian leu, ISO4217Code, RON]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RON Context triple: [Romanian leu, ISO4217Code, RON]
-
A.
RON
chosen
RON is the official currency code for the Romanian leu used in international finance and currency exchange.
-
B.
RO
RO is the IATA airline designator assigned to TAROM, the flag carrier airline of Romania.
-
C.
RO
RO is the stock ticker symbol for Roche, the multinational Swiss healthcare and pharmaceutical company.
-
D.
Ros
Ros is a given name and surname used in various cultures, often as a short form or variant of names like Ross, Rosalind, or Rosemary.
-
E.
REN
REN is a blockchain-based project and protocol focused on enabling cross-chain liquidity and interoperability between different cryptocurrency networks.
- 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_69ca834ca1c88190a11ffb0200342fac |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc479999c881908c0c4e01c07d02d4 |
completed | March 31, 2026, 10:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cebc42922c819099a464d2e347dec4 |
completed | April 2, 2026, 6:58 p.m. |
Created at: March 30, 2026, 6:28 p.m.