Triple

T21227349
Position Surface form Disambiguated ID Type / Status
Subject Gateway Mobile Switching Centre E523116 entity
Predicate retrieves P75152 FINISHED
Object routing information for called mobile subscriber 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: routing information for called mobile subscriber | Statement: [Gateway Mobile Switching Centre, retrieves, routing information for called mobile subscriber]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: retrieves
Context triple: [Gateway Mobile Switching Centre, retrieves, routing information for called mobile subscriber]
  • A. obtains chosen
    Indicates that one entity comes into possession or control of another entity, typically through some action or process.
  • B. retrievalOutcome
    Indicates the result or status produced when an attempt is made to retrieve something.
  • C. receives
    Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
  • D. retrievedBy
    Indicates that one entity has obtained, fetched, or recovered another entity, typically from a source or storage location.
  • E. returns
    Indicates that one entity gives or sends something back to another entity, often as a result or outcome of a process or action.
  • 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_69e0b512ad94819087942b2ed925185f completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e734ac42a08190b95a24acf5f0779b completed April 21, 2026, 8:26 a.m.
PD Predicate disambiguation batch_69e5f60e1a888190ba75e2e900270a4e completed April 20, 2026, 9:46 a.m.
Created at: April 16, 2026, 3:44 p.m.