Triple
T32183056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XLNX |
E822034
|
entity |
| Predicate | associatedWithReportingCurrency |
P194590
|
FINISHED |
| Object | USD |
E105
|
NE 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: [XLNX, associatedWithReportingCurrency, USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithReportingCurrency Context triple: [XLNX, associatedWithReportingCurrency, USD]
-
A.
associatedCurrencyCode
Indicates the currency code that is linked to or used in connection with the given entity or transaction.
-
B.
hasAssociatedCurrencyEntity
Indicates that an entity is linked to a specific currency entity that represents the monetary unit relevant to it.
-
C.
backedCurrencyWith
Indicates that one currency is supported or guaranteed in value by reserves or assets held in another currency.
-
D.
hasUnitOfAccount
chosen
Indicates that a value or quantity is expressed in terms of a particular monetary or measurement unit used for accounting or valuation.
-
E.
involvesCurrency
Indicates that the relationship or action includes or pertains to the use, exchange, or specification of a particular currency.
- F. None of above.
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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0be0fbe88190a1f34d8f161ca607 |
completed | June 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:34 a.m.