Triple
T35077782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netscape IPO |
E1012351
|
entity |
| Predicate | offeredSecurityType |
P3487
|
FINISHED |
| Object | common stock |
—
|
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: common stock | Statement: [Netscape IPO, offeredSecurityType, common stock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredSecurityType Context triple: [Netscape IPO, offeredSecurityType, common stock]
-
A.
securityTypeListed
Indicates that a security is officially listed and traded on a recognized exchange or trading venue.
-
B.
securityType
chosen
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
-
C.
securityTypePermitted
Indicates that a particular type or category of security is allowed or authorized within a given context or system.
-
D.
typeOfSecurityAddressed
Indicates the category or kind of security concern, risk, or protection that is being addressed in a given context.
-
E.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: May 3, 2026, 4:01 p.m.