Triple
T8806591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BORL |
E209547
|
entity |
| Predicate | exchangeCurrency |
P84714
|
FINISHED |
| Object | 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: USD | Statement: [BORL, exchangeCurrency, USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangeCurrency Context triple: [BORL, exchangeCurrency, USD]
-
A.
currencyProject
Indicates a relationship where a project is associated with, uses, or is denominated in a particular currency.
-
B.
exchangeRateToPoundSterling
Indicates the rate at which one unit of a given currency can be converted into British pounds sterling.
-
C.
exchangeSymbol
Indicates that one entity serves as the ticker or trading symbol used to represent another entity on a specific exchange.
-
D.
currencyPlanned
Indicates that a specific currency is intended or scheduled to be used in a planned transaction, budget, or financial arrangement.
-
E.
currencyInterchangeabilityAgreementSince
Indicates that two or more currencies have been mutually accepted as interchangeable under a formal agreement starting from a specified point in time.
- 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_69ca836320e48190b5cf585b90a322c4 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fd1f1a08190a2e584f6b0495f5c |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:45 p.m.