Triple

T10624601
Position Surface form Disambiguated ID Type / Status
Subject H3RC E250289 entity
Predicate associatedWithMMSINumber P5467 FINISHED
Object 353136000 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: 353136000 | Statement: [H3RC, associatedWithMMSINumber, 353136000]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedWithMMSINumber
Context triple: [H3RC, associatedWithMMSINumber, 353136000]
  • A. MMSINumber
    Indicates a relationship where a mobile subscriber is associated with a specific Mobile Station International ISDN Number (MSISDN) used to identify their phone line in a mobile network.
  • B. associatedNumber chosen
    Indicates a relationship where a specific number is linked or assigned to an entity as its associated value.
  • C. associatedFlagCarrier
    Indicates that one entity serves as the designated national or primary flag carrier airline associated with another entity (such as a country, region, or organization).
  • D. hasMVNO
    Indicates that one entity operates as a Mobile Virtual Network Operator (MVNO) using the network infrastructure or services provided by another entity.
  • E. telecommunicationsProvider
    Indicates that one entity provides telecommunications services (such as phone, internet, or data connectivity) to another entity.
  • 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_69d6aa5993448190a493b790b8f85010 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6df7fe9fc81908b3b8d1dc06a829c completed April 8, 2026, 11:06 p.m.
PD Predicate disambiguation batch_69d6dd7fae088190973f70c69738af49 completed April 8, 2026, 10:58 p.m.
Created at: April 8, 2026, 8:53 p.m.