Triple
T32183051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XLNX |
E822034
|
entity |
| Predicate | associatedWithSecurityType |
—
|
GENERATED |
| Object | common stock |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSecurityType Context triple: [XLNX, associatedWithSecurityType, common stock]
-
A.
assignedToSecurityType
Indicates that something has been designated or linked to a particular security classification or security instrument type.
-
B.
securityType
chosen
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
-
C.
securityTypeListed
Indicates that a security is officially listed and traded on a recognized exchange or trading venue.
-
D.
securityTypePermitted
Indicates that a particular type or category of security is allowed or authorized within a given context or system.
-
E.
hasSecuritySubtype
Indicates that one security is a more specific subtype or classification of another security within a security hierarchy or taxonomy.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 1, 2026, 12:34 a.m.