Triple
T35077790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netscape IPO |
E1012351
|
entity |
| Predicate | initialPriceRangePerShare |
P191721
|
FINISHED |
| Object | 12 USD to 14 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: 12 USD to 14 USD | Statement: [Netscape IPO, initialPriceRangePerShare, 12 USD to 14 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialPriceRangePerShare Context triple: [Netscape IPO, initialPriceRangePerShare, 12 USD to 14 USD]
-
A.
revisedPriceRangePerShare
Indicates the updated range of prices assigned to each individual share after a revision or adjustment.
-
B.
offerPricePerShare
Indicates the monetary amount proposed or requested for each individual share in a transaction or offer.
-
C.
initialPriceTarget
Indicates the originally set price level that an analyst or entity targets for an asset before any subsequent revisions.
-
D.
hasMarketPriceRange
Indicates that an entity is associated with a specified range of possible market prices at which it can be bought or sold.
-
E.
priceAtFounding
Indicates the monetary price or valuation associated with an entity at the time it was founded.
- 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_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:01 p.m.