Triple
T14894911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASDAQ:LBTYK |
E359845
|
entity |
| Predicate | hasVotingPowerPerShare |
P116571
|
FINISHED |
| Object | 0 votes per share |
—
|
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: 0 votes per share | Statement: [NASDAQ:LBTYK, hasVotingPowerPerShare, 0 votes per share]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVotingPowerPerShare Context triple: [NASDAQ:LBTYK, hasVotingPowerPerShare, 0 votes per share]
-
A.
hasVotingStake
Indicates that one entity possesses a share of voting power or decision-making authority in another entity.
-
B.
hasVotingPower
Indicates that an entity possesses the authority or capacity to participate in a decision-making or electoral process by casting votes.
-
C.
hasRelativeVotingPower
Indicates that one entity possesses a specified level or proportion of voting power relative to another entity or group.
-
D.
hasDifferentVotingRightsFrom
Indicates that two entities possess voting rights that are not identical in terms of scope, weight, or conditions.
-
E.
hasNumberOfVotingMembers
Indicates the specific count of individuals who hold voting rights within a given group or body.
- 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.