Triple
T21786293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAM |
E537845
|
entity |
| Predicate | hasPegType |
P74319
|
FINISHED |
| Object | fixed exchange rate peg |
—
|
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 peg | Statement: [BAM, hasPegType, fixed exchange rate peg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPegType Context triple: [BAM, hasPegType, fixed exchange rate peg]
-
A.
typeOfPeg
chosen
Indicates that one entity is a specific kind or category of peg in relation to another entity.
-
B.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
hasParType
Indicates that an entity has a specific parent type or category to which it belongs.
-
D.
hasPetrovType
Indicates that an entity (typically a spacetime or gravitational field) is classified as having a specific Petrov type in the Petrov classification of its Weyl tensor.
-
E.
hasParticleType
Indicates that an entity is associated with, composed of, or characterized by a specific type or category of particle.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0621b5d6881908b74bc999c94fa3d |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.