Triple
T35077786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Netscape IPO |
E1012351
|
entity |
| Predicate | underwriter |
P184608
|
FINISHED |
| Object | Morgan Stanley |
—
|
NE NERFINISHED |
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: Morgan Stanley | Statement: [Netscape IPO, underwriter, Morgan Stanley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underwriter Context triple: [Netscape IPO, underwriter, Morgan Stanley]
-
A.
underwriterOfIPO
chosen
Indicates that an entity serves as the underwriter responsible for managing and facilitating a specific initial public offering (IPO).
-
B.
lender
Indicates a relationship where one party provides something, typically money or resources, to another with the expectation of repayment or return.
-
C.
borrower
Indicates a relationship where one entity temporarily receives and uses something belonging to another entity, typically with the obligation to return it.
-
D.
lenderType
Indicates the classification or category of the lender involved in a lending relationship (e.g., bank, individual, institution).
-
E.
under
Indicates that one entity is positioned below or beneath another entity, often implying vertical alignment or coverage.
- 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_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 3, 2026, 4:01 p.m.