Triple
T8494807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPCE |
E201070
|
entity |
| Predicate | hasIPODate |
P37854
|
FINISHED |
| Object | 2019-10-28 |
—
|
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: 2019-10-28 | Statement: [SPCE, hasIPODate, 2019-10-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIPODate Context triple: [SPCE, hasIPODate, 2019-10-28]
-
A.
hasIPO
Indicates that a company or organization has undergone an initial public offering (IPO), establishing a relationship between the entity and its stock market listing event.
-
B.
hasUnderlyingCompanyIPOApproxYear
chosen
Indicates the approximate calendar year in which the underlying company completed its initial public offering (IPO).
-
C.
IPOStatus
Indicates the relationship between an entity and its stage or condition in the process of becoming a publicly traded company through an initial public offering.
-
D.
inceptionDate
Indicates the date on which an entity, event, or relationship was first created, established, or began to exist.
-
E.
issuerFoundedAs
Indicates that the issuer was originally established or created under a particular prior name, form, or organizational identity.
- 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.