Triple

T3196536
Position Surface form Disambiguated ID Type / Status
Subject NSFNET E66947 entity
Predicate decommissionReason P10134 FINISHED
Object maturation of commercial Internet infrastructure 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: maturation of commercial Internet infrastructure | Statement: [NSFNET, decommissionReason, maturation of commercial Internet infrastructure]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: decommissionReason
Context triple: [NSFNET, decommissionReason, maturation of commercial Internet infrastructure]
  • A. decommissionedReason chosen
    Indicates the reason or cause for which an entity, typically an asset or system, was taken out of service or formally retired.
  • B. decommissionedDate
    Indicates the date on which an entity was formally taken out of service or retired from active use.
  • C. decommissioningStartDate
    Indicates the date on which the process of taking an asset or system out of active service is initiated.
  • D. inactivationReason
    Indicates the reason or cause for which an entity, status, or process has been deactivated or made inactive.
  • E. reasonForDisbandment
    Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
  • 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_69ad8588ba18819086a10951c32ecb80 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada7177b488190b7a1b40ff3fae15f completed March 8, 2026, 4:43 p.m.
PD Predicate disambiguation batch_69ad9e05e4f48190adbe4366cdba2349 completed March 8, 2026, 4:04 p.m.
Created at: March 8, 2026, 3:07 p.m.