Triple

T11380389
Position Surface form Disambiguated ID Type / Status
Subject Media Transfer Protocol E269577 entity
Predicate transportLayer P10376 FINISHED
Object IP E123425 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: IP | Statement: [Media Transfer Protocol, transportLayer, IP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IP
Context triple: [Media Transfer Protocol, transportLayer, IP]
  • A. IP
    IP is the acronym for Infraestruturas de Portugal, the Portuguese state-owned company responsible for managing the country’s road and rail infrastructure.
  • B. IP
    IP is the stock ticker symbol for International Paper, a major global producer of paper and packaging products.
  • C. IP chosen
    IP (Internet Protocol) is the core networking protocol that defines how data is addressed and routed across interconnected computer networks such as the internet.
  • D. ips
    ips is an IETF working group focused on developing standards for transporting storage protocols over IP networks.
  • E. INETER
    INETER is Nicaragua’s national geophysical and meteorological institute responsible for monitoring volcanic, seismic, and other natural hazards across the country.
  • 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_69d6aacca1048190b39dbbc2174616fa completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7fc331f188190a7f69f1aae53fb6b completed April 9, 2026, 7:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69e556a99c8c8190b7439a548216e648 completed April 19, 2026, 10:26 p.m.
Created at: April 8, 2026, 9:34 p.m.