Triple
T22239424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DB1 |
E549679
|
entity |
| Predicate | hasCorporateActionEligibility |
P109268
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [DB1, hasCorporateActionEligibility, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorporateActionEligibility Context triple: [DB1, hasCorporateActionEligibility, yes]
-
A.
hasCorporateActionsOn
Indicates that one entity performs, records, or is associated with corporate actions (such as dividends, splits, or mergers) that affect another entity.
-
B.
hasCorporateActionHistory
Indicates that an entity is associated with a record or sequence of past corporate actions or events that have affected it.
-
C.
dividendEligibility
chosen
Indicates that an entity (such as a shareholder or security) qualifies to receive a declared dividend for a given distribution event.
-
D.
alsoEligible
Indicates that an entity qualifies for an additional option, status, or benefit beyond its primary or initial eligibility.
-
E.
branchEligibility
Indicates whether an entity meets the conditions required to qualify for a particular branch, option, or subdivision within a larger system or structure.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f132133b908190b0fb32a5ee68e1e6 |
completed | April 28, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:38 p.m.