Triple
T35077792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netscape IPO |
E1012351
|
entity |
| Predicate | firstDayClosingPricePerShare |
P206831
|
FINISHED |
| Object | 58.25 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: 58.25 USD | Statement: [Netscape IPO, firstDayClosingPricePerShare, 58.25 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDayClosingPricePerShare Context triple: [Netscape IPO, firstDayClosingPricePerShare, 58.25 USD]
-
A.
cappingDate
Indicates the date on which a limit, cap, or maximum condition is set, becomes effective, or is reached for the related entities or values.
-
B.
finalDay
Indicates that a given day is the last or concluding day within a specified period, event, or sequence.
-
C.
openingDay
Indicates the specific day on which something, typically an event, season, or venue, officially begins or first opens to the public.
-
D.
closingPosition
Indicates that an entity terminates, finalizes, or brings to an end the position or state of another entity.
-
E.
firstUnitsClosed
Indicates that the initial set of units in a sequence, batch, or process has been completed or closed.
- 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_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.