Triple
T8494805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPCE |
E201070
|
entity |
| Predicate | hasCorporateAction |
P41812
|
FINISHED |
| Object | reverse stock split 1-for-20 in 2024 |
—
|
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: reverse stock split 1-for-20 in 2024 | Statement: [SPCE, hasCorporateAction, reverse stock split 1-for-20 in 2024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCorporateAction Context triple: [SPCE, hasCorporateAction, reverse stock split 1-for-20 in 2024]
-
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
chosen
Indicates that an entity is associated with a record or sequence of past corporate actions or events that have affected it.
-
C.
hasAct
Indicates that an entity performs, participates in, or is associated with a specific act or action.
-
D.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
E.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe57c01f881908cb77c8c834ac08d |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.