Triple

T20739024
Position Surface form Disambiguated ID Type / Status
Subject dot-com bubble E509788 entity
Predicate involvedInstrument P19640 FINISHED
Object initial public offerings 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: initial public offerings | Statement: [dot-com bubble, involvedInstrument, initial public offerings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: involvedInstrument
Context triple: [dot-com bubble, involvedInstrument, initial public offerings]
  • A. playedInstrument
    Indicates that an entity performed or used a particular musical instrument.
  • B. studiedByInstrument
    Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
  • C. instrumentalIn chosen
    Indicates that one entity serves as a crucial means, tool, or contributing factor in bringing about an outcome or enabling another entity’s action or effect.
  • D. usedAsInstrumentBy
    Indicates that one entity functions as a tool, means, or instrument through which another entity performs an action or achieves an effect.
  • E. influencedInstrument
    Indicates that one entity has affected, shaped, or altered a musical instrument or tool in some way, such as its design, use, style, or development.
  • 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_69e0b4c589c08190834fb5d86d0efa2b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c20c36708190898b889b6989fc7d completed April 21, 2026, 12:17 a.m.
PD Predicate disambiguation batch_69e5c04b31248190b9b9d91b5cb854e3 completed April 20, 2026, 5:57 a.m.
Created at: April 16, 2026, 12:32 p.m.