Triple
T3359501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DJF |
E70684
|
entity |
| Predicate | peggedType |
P19140
|
FINISHED |
| Object | fixed exchange rate |
—
|
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: fixed exchange rate | Statement: [DJF, peggedType, fixed exchange rate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peggedType Context triple: [DJF, peggedType, fixed exchange rate]
-
A.
isPegged
Indicates that one entity’s value, status, or behavior is fixed or tightly linked to that of another entity, typically so that changes in the reference entity directly determine changes in the pegged entity.
-
B.
specType
Indicates the specific type or category of a specification that an entity is associated with.
-
C.
syntacticType
Indicates the grammatical or structural category that characterizes how an expression functions within a syntactic construction.
-
D.
pegType
chosen
Indicates the specific category or kind of peg associated with or assigned to an entity.
-
E.
symbolType
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
- 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb266c4a881908aded39ccb8f43b2 |
completed | March 8, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69ada42fbe7c8190b9f185b5ab985f17 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.