Triple
T8694637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank Indonesia Act |
E206376
|
entity |
| Predicate | establishesObjective |
P5437
|
FINISHED |
| Object | rupiah stability |
—
|
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: rupiah stability | Statement: [Bank Indonesia Act, establishesObjective, rupiah stability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishesObjective Context triple: [Bank Indonesia Act, establishesObjective, rupiah stability]
-
A.
initialGoal
Indicates that something represents the first or starting objective or target in a sequence of goals.
-
B.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
C.
notableObjective
Indicates that an entity has a significant, distinguished, or widely recognized goal, purpose, or target associated with it.
-
D.
strategicGoal
chosen
Indicates that one entity represents a long-term objective or desired outcome that another entity is intentionally aiming to achieve or align actions toward.
-
E.
goalDescription
Indicates that an entity expresses, specifies, or provides a textual description of a goal or intended outcome associated with another entity or activity.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58284c58819091beb05a7d6b3a1b |
completed | March 31, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.