Triple
T1241104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lebanese pound |
E26658
|
entity |
| Predicate | historicalPegRate |
P13429
|
FINISHED |
| Object | 1507.5 LBP per USD |
—
|
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: 1507.5 LBP per USD | Statement: [Lebanese pound, historicalPegRate, 1507.5 LBP per USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPegRate Context triple: [Lebanese pound, historicalPegRate, 1507.5 LBP per USD]
-
A.
historicalPeg
chosen
Indicates a relationship where one entity’s value, status, or definition was formerly fixed or tied to another entity in the past.
-
B.
hasInflationHistory
Indicates that an entity is associated with a recorded or known pattern of inflation over time.
-
C.
hasDenominationHistory
Indicates that an entity has an associated record or sequence of changes in its denomination over time.
-
D.
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.
-
E.
replacedCurrencyAtRate
Indicates that one currency was substituted for another at a specified exchange rate.
- 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_69a4948689d08190b3a4a3f388c02148 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf4343e48190a232abd8475880a0 |
completed | March 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69a4bb696a38819095845c84f0241287 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.