Triple
T29893842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial credit |
E759223
|
entity |
| Predicate | standardCurrencyOf |
P78277
|
FINISHED |
| Object | Galactic Empire |
—
|
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: Galactic Empire | Statement: [Imperial credit, standardCurrencyOf, Galactic Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardCurrencyOf Context triple: [Imperial credit, standardCurrencyOf, Galactic Empire]
-
A.
localCurrency
chosen
Indicates that a particular currency is officially used or recognized as the standard medium of exchange within a specific locality, region, or country.
-
B.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
C.
currencyCodeDenoted
Indicates that a specific currency code is used to denote or represent a particular currency.
-
D.
mainCurrencyContext
Indicates that one currency is designated as the primary or reference currency within a given financial or transactional context.
-
E.
currencySignAdopted
Indicates that a particular currency sign has been officially adopted for use with a given currency or monetary 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 29, 2026, 6:03 p.m.