Triple
T6040697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RWF |
E134535
|
entity |
| Predicate | symbol |
P129
|
FINISHED |
| Object | R₣ |
E564752
|
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: R₣ | Statement: [RWF, symbol, R₣]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: R₣ Context triple: [RWF, symbol, R₣]
-
A.
R₣
chosen
R₣ is the currency sign used to denote the Rwandan franc, the official monetary unit of Rwanda.
-
B.
FR-59
FR-59 is the ISO 3166-2 code for Nord, a department in northern France known for its industrial history and proximity to Belgium.
-
C.
FUK
FUK is the IATA airport code for Fukuoka Airport, a major international and domestic air hub serving the city of Fukuoka in Japan.
-
D.
RIF
RIF (Rule Interchange Format) is a W3C standard designed to enable the exchange and interoperability of rules across different Semantic Web systems and rule engines.
-
E.
FRF
FRF is a NUTS 1 statistical region code designating the French region of Brittany within the European Union’s territorial classification system.
- 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056cf82d481909d5161fe3643e7ed |
completed | March 22, 2026, 8:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c11cfbb4cc81909736d5d041dd0b23 |
completed | March 23, 2026, 10:59 a.m. |
Created at: March 22, 2026, 4:08 p.m.