Triple
T32183061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XLNX |
E822034
|
entity |
| Predicate | associatedWithCUSIP |
P5718
|
FINISHED |
| Object | 983919101 (historical) |
—
|
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: 983919101 (historical) | Statement: [XLNX, associatedWithCUSIP, 983919101 (historical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCUSIP Context triple: [XLNX, associatedWithCUSIP, 983919101 (historical)]
-
A.
hasCUSIP
chosen
Indicates that a financial instrument is associated with a specific CUSIP identifier assigned to it.
-
B.
issuerCUSIP
Indicates that the subject entity is identified as the issuer associated with the specified CUSIP code.
-
C.
associatedWithTicker
Indicates that an entity is linked or connected to a specific stock market ticker symbol.
-
D.
associatedWithCompanyTickerClass
Indicates that an entity is linked to a specific class of a company’s stock identified by its ticker symbol.
-
E.
associatedWithCustom
Indicates a relationship where one entity is linked to or connected with another entity in a non-standard, user-defined, or customized manner.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:34 a.m.