Triple
T26242011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lattice Semiconductor Corporation |
E656340
|
entity |
| Predicate | listedExchangeCountry |
P37744
|
FINISHED |
| Object | United States |
—
|
NE NERFINISHED |
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: United States | Statement: [Lattice Semiconductor Corporation, listedExchangeCountry, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listedExchangeCountry Context triple: [Lattice Semiconductor Corporation, listedExchangeCountry, United States]
-
A.
listingCountry
Indicates the country in which an item, asset, or entity is officially listed or made available.
-
B.
hasSecurityExchangeCountry
Indicates the country in which a given security exchange is located or operates.
-
C.
countryOfListing
chosen
Indicates that a company or financial instrument is officially listed and traded in the specified country’s market or exchange.
-
D.
exchanges
Indicates a reciprocal transfer of something of value between two or more entities.
-
E.
currencyInterchangeabilityAgreementSince
Indicates that two or more currencies have been mutually accepted as interchangeable under a formal agreement starting from a specified point in time.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60d8f7f9c8190bb8cb8f8ac4c0ca5 |
completed | May 2, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:03 p.m.