Triple

T8414661
Position Surface form Disambiguated ID Type / Status
Subject TSM E198703 entity
Predicate hasADRRatio P16308 FINISHED
Object 1 ADR represents 5 common shares 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: 1 ADR represents 5 common shares | Statement: [TSM, hasADRRatio, 1 ADR represents 5 common shares]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasADRRatio
Context triple: [TSM, hasADRRatio, 1 ADR represents 5 common shares]
  • A. hasADR
    Indicates that an entity is associated with an adverse drug reaction (ADR), such as experiencing or being linked to a harmful or unintended response to a medication.
  • B. isADROf
    Indicates a relationship where one entity serves as the Authorized Designated Responsible Officer (ADRO) for another entity, typically bearing formal oversight or accountability on its behalf.
  • C. hasProportion chosen
    Indicates that one entity stands in a specified ratio, fraction, or relative share to another entity or whole.
  • D. hasDRSZones
    Indicates that one entity possesses, defines, or is associated with specific DRS (Disaster Recovery Site or similarly defined) zones.
  • E. hasRatingLevel
    Indicates that an entity is associated with a particular rating level or score category.
  • 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_69ca831201b481909e137936ef99ff11 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cb83e328cc8190b3b038005d0bb66f completed March 31, 2026, 8:20 a.m.
PD Predicate disambiguation batch_69cb70d70ea081909c3dc1bd2ec14f85 completed March 31, 2026, 6:59 a.m.
Created at: March 30, 2026, 6:06 p.m.