Triple
T35077791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netscape IPO |
E1012351
|
entity |
| Predicate | revisedPriceRangePerShare |
P182500
|
FINISHED |
| Object | 21 USD to 24 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: 21 USD to 24 USD | Statement: [Netscape IPO, revisedPriceRangePerShare, 21 USD to 24 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revisedPriceRangePerShare Context triple: [Netscape IPO, revisedPriceRangePerShare, 21 USD to 24 USD]
-
A.
offerPricePerShare
Indicates the monetary amount proposed or requested for each individual share in a transaction or offer.
-
B.
priceChange
Indicates a change in the price of an entity, typically specifying how much and/or in what direction the price has moved over a given period.
-
C.
hasMarketPriceRange
Indicates that an entity is associated with a specified range of possible market prices at which it can be bought or sold.
-
D.
initialPriceTarget
Indicates the originally set price level that an analyst or entity targets for an asset before any subsequent revisions.
-
E.
laterPrice
Indicates that the price of an item at a later time is being specified or related to another (typically earlier) price.
- 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_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78ce43094819093857fc99f269afe |
completed | May 3, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:01 p.m.