Triple
T14894906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASDAQ:LBTYK |
E359845
|
entity |
| Predicate | hasMarketSector |
P116570
|
FINISHED |
| Object | communications services |
—
|
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: communications services | Statement: [NASDAQ:LBTYK, hasMarketSector, communications services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarketSector Context triple: [NASDAQ:LBTYK, hasMarketSector, communications services]
-
A.
hasMarket
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
B.
hasMarketIndex
Indicates that an entity is associated with, or tracked by, a specific market index.
-
C.
hasMarketStructure
Indicates that one entity possesses, follows, or is characterized by a particular market structure in an economic or commercial context.
-
D.
hasMarketFocus
Indicates that an entity concentrates its business activities, products, or services on a particular market or customer segment.
-
E.
hasMarketCommodity
Indicates that an entity is associated with or trades in a particular commodity within a market context.
- F. None of above. chosen
Provenance (4 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f9d10c819091732d7a5a42a682 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:10 a.m.