Triple
T32183068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XLNX |
E822034
|
entity |
| Predicate | associatedWithListingType |
P32980
|
FINISHED |
| Object | primary listing |
—
|
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: primary listing | Statement: [XLNX, associatedWithListingType, primary listing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithListingType Context triple: [XLNX, associatedWithListingType, primary listing]
-
A.
listingType
chosen
Indicates the category or format under which an item, property, or service is offered or advertised (e.g., for sale, for rent, auction, etc.).
-
B.
sharedListingWith
Indicates that one entity has made a listing (such as an item, property, or resource) available jointly or in common with another entity.
-
C.
hasListingNumber
Indicates that an entity is associated with a specific listing identification number.
-
D.
hasListedProductType
Indicates that an entity has a product associated with it that is categorized under a specific listed product type.
-
E.
hasParentListing
Indicates that an item or listing is associated with a higher-level or primary listing from which it derives or to which it belongs.
- 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.