Triple
T28653670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vahun |
E725269
|
entity |
| Predicate | sharesNationalCurrency |
P18115
|
FINISHED |
| Object | Liberian dollar |
—
|
NE NERFINISHED |
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: Liberian dollar | Statement: [Vahun, sharesNationalCurrency, Liberian dollar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesNationalCurrency Context triple: [Vahun, sharesNationalCurrency, Liberian dollar]
-
A.
currencyCountry
Indicates that a given currency is officially used as legal tender in a particular country.
-
B.
currencyFamily
Indicates that two currencies belong to the same broader monetary family or classification, typically sharing a common origin, standard, or structural framework.
-
C.
currencyOrEconomy
Indicates that there is a relationship involving the type, status, or characteristics of a currency or economic system associated with an entity.
-
D.
currencyArea
chosen
Indicates that one entity is the geographic or economic region in which the other entity’s currency is officially used or valid.
-
E.
currencyScope
Indicates the range or jurisdiction within which a particular currency is valid, applicable, or intended to be used.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 28, 2026, 4:53 a.m.