Triple
T15902509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burmese rupee |
E385623
|
entity |
| Predicate | introducedAsSeparateFrom |
P62524
|
FINISHED |
| Object | Indian rupee in 1937 |
—
|
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: Indian rupee in 1937 | Statement: [Burmese rupee, introducedAsSeparateFrom, Indian rupee in 1937]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsSeparateFrom Context triple: [Burmese rupee, introducedAsSeparateFrom, Indian rupee in 1937]
-
A.
introducedAsSeparateCurrency
chosen
Indicates that one currency was formally established and began circulating as a distinct, independent currency separate from a previously used or shared currency.
-
B.
introducedAlongWith
Indicates that one entity was introduced or presented at the same time as another entity, as part of a joint or concurrent introduction.
-
C.
developedApartFrom
Indicates that two entities were developed independently of each other, without direct influence, coordination, or shared development processes.
-
D.
introducedVia
Indicates that one entity was brought to the attention, presence, or awareness of another entity through a specific intermediary, method, or channel.
-
E.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142ca3b208190946c3aa4c1e6087c |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:52 a.m.