Triple
T23790628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LVS |
E588080
|
entity |
| Predicate | associatedCompanyStockExchangeTicker |
P33802
|
FINISHED |
| Object | LVS |
—
|
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: LVS | Statement: [LVS, associatedCompanyStockExchangeTicker, LVS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCompanyStockExchangeTicker Context triple: [LVS, associatedCompanyStockExchangeTicker, LVS]
-
A.
associatedCompanyTickerSuccessor
Indicates that one company ticker symbol is the successor or replacement for another company ticker symbol in an association or mapping.
-
B.
underlyingCompanyTicker
Indicates that one entity is the stock ticker symbol corresponding to the underlying company of another financial instrument or entity.
-
C.
parentCompanyTicker
Indicates the stock market ticker symbol associated with the parent company of a given entity.
-
D.
underlyingCompanyPrimaryListingTicker
chosen
Indicates the stock ticker symbol of the primary exchange listing for the underlying company.
-
E.
acquiringCompanyTicker
Indicates the stock ticker symbol of the company that is acquiring another company in a transaction.
- 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_69e2490f4ad48190b690878eec3596c6 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c6d73cf8819099fd8cbb9f93a908 |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:17 p.m.