Triple
T2951811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BRK.A |
E79836
|
entity |
| Predicate | hasShareSplitHistory |
P41812
|
FINISHED |
| Object | no regular 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: no regular stock splits | Statement: [BRK.A, hasShareSplitHistory, no regular stock splits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShareSplitHistory Context triple: [BRK.A, hasShareSplitHistory, no regular stock splits]
-
A.
hasCorporateActionHistory
chosen
Indicates that an entity is associated with a record or sequence of past corporate actions or events that have affected it.
-
B.
hasInflationHistory
Indicates that an entity is associated with a recorded or known pattern of inflation over time.
-
C.
hasDenominationHistory
Indicates that an entity has an associated record or sequence of changes in its denomination over time.
-
D.
hasHistoricalShiftFrom
Indicates a relationship where one state, practice, or condition has been replaced or transformed over time from another earlier state, practice, or condition.
-
E.
hasShareClass
Indicates that an entity is associated with a specific class or category of shares that defines distinct rights or characteristics of ownership.
- 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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98fcea5c8190b7d80de942bcb4f7 |
completed | March 8, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69ad960a70ac8190816b5ae3e8631031 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.