Triple
T2716658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RCI.B |
E59980
|
entity |
| Predicate | hasCorporateActionHistory |
P41812
|
FINISHED |
| Object | stock splits |
—
|
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: stock splits | Statement: [RCI.B, hasCorporateActionHistory, stock splits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorporateActionHistory Context triple: [RCI.B, hasCorporateActionHistory, stock splits]
-
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.
operatorHistory
Indicates a record of past actions, states, or changes associated with a particular operator over time.
-
C.
ownershipHistory
Indicates the sequence of past and present owners associated with an entity over time.
-
D.
hasPolicyHistory
Indicates that an entity is associated with a record or sequence of past policies that have applied to it over time.
-
E.
sponsorHistory
Indicates that one entity has previously acted as a sponsor for another entity or event over time.
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda964d4881908179b2a1b16411e4 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8240920819087a812d816a55edb |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd949c120819099a9d56eb71a0339 |
completed | March 7, 2026, 7:52 a.m. |
Created at: March 6, 2026, 9:55 p.m.