Triple

T16825580
Position Surface form Disambiguated ID Type / Status
Subject Signaling System No. 7 E409009 entity
Predicate hasComponent P35 FINISHED
Object MTP Level 3 E1237378 NE 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: MTP Level 3 | Statement: [Signaling System No. 7, hasComponent, MTP Level 3]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MTP Level 3
Context triple: [Signaling System No. 7, hasComponent, MTP Level 3]
  • A. MTP Level 3 chosen
    MTP Level 3 is the network layer of the SS7 signaling system responsible for message routing, traffic management, and linkset reliability across the signaling network.
  • B. MTP Level 2
    MTP Level 2 is the Signaling System No. 7 (SS7) protocol layer responsible for reliable, error-checked transfer of signaling messages over a physical link.
  • C. MTP Level 1
    MTP Level 1 is the physical layer of the SS7 signaling system, defining the electrical, functional, and procedural characteristics for transmitting signaling data over communication links.
  • D. Level 3.1
    Level 3.1 is a specific H.264/AVC profile level that defines constraints on video resolution, bitrate, and processing requirements for compatible encoders and decoders.
  • E. MTP
    MTP is the National Rail station code for Montpelier railway station in Bristol, England.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d88394566c8190b3dcbdc72935f7fa completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b3126db88190ac5595b0d50e4232 completed April 18, 2026, 4:36 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00c79cdf9c8190aa20d536ca17ab81 completed May 10, 2026, 5:59 p.m.
Created at: April 10, 2026, 5:23 a.m.