Triple
T4092529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AutoZone, Inc. |
E87734
|
entity |
| Predicate | primaryReportingCurrency |
P34551
|
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: [AutoZone, Inc., primaryReportingCurrency, USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryReportingCurrency Context triple: [AutoZone, Inc., primaryReportingCurrency, USD]
-
A.
majorCurrencyPair
Indicates that the two currencies form a widely traded, highly liquid foreign-exchange pair considered significant in global markets.
-
B.
representsOfficialCurrency
Indicates that one entity serves as the official legal tender or primary currency used within the jurisdiction or authority of another entity.
-
C.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
D.
currencyOfOfficialReports
chosen
Indicates the currency in which an entity’s official reports or financial statements are formally presented.
-
E.
previousCurrency
Indicates that one currency served as the predecessor or was replaced by another currency in a monetary system or sequence.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefcae22a081908af65a960306b78c |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:40 p.m.