Triple
T35077797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netscape IPO |
E1012351
|
entity |
| Predicate | companyAgeAtIPO |
P193382
|
FINISHED |
| Object | about 16 months |
—
|
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: about 16 months | Statement: [Netscape IPO, companyAgeAtIPO, about 16 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyAgeAtIPO Context triple: [Netscape IPO, companyAgeAtIPO, about 16 months]
-
A.
IPOYear
Indicates the year in which an entity first became a publicly traded company through an initial public offering (IPO).
-
B.
hasUnderlyingCompanyIPOApproxYear
Indicates the approximate calendar year in which the underlying company completed its initial public offering (IPO).
-
C.
hasYearOfEstablishment
Indicates the specific year in which an entity was founded, created, or formally established.
-
D.
companyFoundedAt
Indicates that a company was established or came into existence at a specific location.
-
E.
underlyingCompanyFormationYear
Indicates the calendar year in which the referenced underlying company was originally formed or established.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69fd4445f8c08190bb2dc27e0971c55d |
completed | May 8, 2026, 2:02 a.m. |
Created at: May 3, 2026, 4:01 p.m.