Triple
T3731686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhutanese ngultrum |
E79077
|
entity |
| Predicate | coCirculatesWith |
P51324
|
FINISHED |
| Object | Indian rupee in Bhutan |
—
|
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 Bhutan | Statement: [Bhutanese ngultrum, coCirculatesWith, Indian rupee in Bhutan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coCirculatesWith Context triple: [Bhutanese ngultrum, coCirculatesWith, Indian rupee in Bhutan]
-
A.
hasCirculationFeature
Indicates that an entity possesses a specific feature related to movement or flow within a system, such as circulation paths, routes, or mechanisms.
-
B.
circulatedAs
Indicates that something was distributed, shared, or passed around in the form or role specified by the related entity.
-
C.
circulatesIn
Indicates that something moves or flows repeatedly within a particular space, system, or medium.
-
D.
hasPrimaryCirculation
Indicates that an entity possesses or is associated with a main or principal system, route, or pattern of circulation (such as movement, flow, or distribution).
-
E.
sharesLibrariesWith
Indicates that two entities use or depend on at least one of the same libraries or library components.
- F. None of above. chosen
Provenance (4 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb21002c81908438170ed6f6c271 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc45debe48190b1c1f894e02b0316 |
completed | March 8, 2026, 6:47 p.m. |
Created at: March 8, 2026, 3:34 p.m.