Triple
T35077789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netscape IPO |
E1012351
|
entity |
| Predicate | offeringPricePerShare |
P87929
|
FINISHED |
| Object | 28 USD |
—
|
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: 28 USD | Statement: [Netscape IPO, offeringPricePerShare, 28 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeringPricePerShare Context triple: [Netscape IPO, offeringPricePerShare, 28 USD]
-
A.
offerPricePerShare
chosen
Indicates the monetary amount proposed or requested for each individual share in a transaction or offer.
-
B.
initialPriceRangePerShare
Indicates the price interval at which each share was originally offered or valued at the start of a specified period or event.
-
C.
revisedPriceRangePerShare
Indicates the updated range of prices assigned to each individual share after a revision or adjustment.
-
D.
offeredAmount
Indicates the specific quantity or value that one party proposes to give or pay to another in the context of an offer.
-
E.
sharesOffered
Indicates that one party has made a certain number or portion of shares available to another party or to the public.
- 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_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: May 3, 2026, 4:01 p.m.