Triple
T11241310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class C common stock |
E266078
|
entity |
| Predicate | primaryHoldersInclude |
P98633
|
FINISHED |
| Object | public investors |
—
|
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: public investors | Statement: [Class C common stock, primaryHoldersInclude, public investors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryHoldersInclude Context triple: [Class C common stock, primaryHoldersInclude, public investors]
-
A.
previousHoldersInclude
Indicates that among the entities that have held a particular role, position, or item in the past, at least one is included in the referenced set of entities.
-
B.
eligibleHolders
Indicates which entities are permitted or qualified to hold or possess a given item, right, or role.
-
C.
includesHoldingsFrom
Indicates that one entity’s set of holdings incorporates or contains the holdings originating from another entity.
-
D.
primaryHold
Indicates that one entity serves as the main or most important holder or custodian of another entity.
-
E.
alsoHeldByFirstHolder
Indicates that something possessed or held by a second holder is (or was) also possessed or held by the first holder.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e919eaf48190a1457851cfc56afb |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d7878906f48190b63ddc103a0c8f9b |
completed | April 9, 2026, 11:03 a.m. |
| PDg | Predicate description generation | batch_69d796cf74308190a5b29d0dd82954a2 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:30 p.m.