Triple

T1180341
Position Surface form Disambiguated ID Type / Status
Subject GPON E25120 entity
Predicate usesArchitecture P24956 FINISHED
Object passive optical splitter network 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: passive optical splitter network | Statement: [GPON, usesArchitecture, passive optical splitter network]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesArchitecture
Context triple: [GPON, usesArchitecture, passive optical splitter network]
  • A. cpuArchitecture
    Indicates the type of processor instruction set or hardware architecture that a computing system or component is designed to run on.
  • B. graphicsArchitecture
    Indicates the underlying design or structural framework that defines how a system’s graphics or visual rendering components are organized and operate.
  • C. usesSoftware
    Indicates that one entity employs or operates a particular software application or system to perform tasks or functions.
  • D. hardwareUsedBy
    Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
  • E. isBuiltFor
    Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
  • F. None of above. chosen

Provenance (4 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_69a494267b4c819088c97a59182bf56a completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bd32c5f48190b4e2d39fa052cbb7 completed March 1, 2026, 10:26 p.m.
PD Predicate disambiguation batch_69a4bb59ca6c81908597a81646674aaa completed March 1, 2026, 10:19 p.m.
PDg Predicate description generation batch_69a4bc6d5b7881908091e40c8695ef53 completed March 1, 2026, 10:23 p.m.
Created at: March 1, 2026, 7:45 p.m.