Triple

T64000
Position Surface form Disambiguated ID Type / Status
Subject net neutrality E1271 entity
Predicate historicalRoot P1823 FINISHED
Object common carrier principles in telephone regulation 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: common carrier principles in telephone regulation | Statement: [net neutrality, historicalRoot, common carrier principles in telephone regulation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalRoot
Context triple: [net neutrality, historicalRoot, common carrier principles in telephone regulation]
  • A. historicalOrigin chosen
    Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
  • B. hasHistoricalOrigin
    Indicates that something originated, was first established, or came into existence during a specific historical period or context.
  • C. historicallyBorneBy
    Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
  • D. historicalFunction
    Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
  • E. historicalRegion
    Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
  • 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_69a24ba4f760819081f6638a3c70538a completed Feb. 28, 2026, 1:57 a.m.
NER Named-entity recognition batch_69a24fd16c248190a6ee4cd96c388772 completed Feb. 28, 2026, 2:15 a.m.
PD Predicate disambiguation batch_69a24ea3c44081908fa3856969881d1f completed Feb. 28, 2026, 2:10 a.m.
Created at: Feb. 28, 2026, 2:02 a.m.