Triple

T364180
Position Surface form Disambiguated ID Type / Status
Subject Boltzmann machines E7922 entity
Predicate hasNetworkType P3937 FINISHED
Object recurrent neural 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: recurrent neural network | Statement: [Boltzmann machines, hasNetworkType, recurrent neural network]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNetworkType
Context triple: [Boltzmann machines, hasNetworkType, recurrent neural network]
  • A. networkType chosen
    Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
  • B. hasServiceType
    Indicates that an entity is associated with or categorized by a particular type of service.
  • C. hasPlatformType
    Indicates that an entity is associated with or characterized by a specific type or category of platform.
  • D. hasNetworkPartner
    Indicates that an entity is connected to another entity through a formal or recognized network partnership relationship.
  • E. hasTeleconnectionsWith
    Indicates a relationship where changes or variations in one system, region, or variable are statistically linked to corresponding changes in another, often distant, system, region, or variable.
  • 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_69a2e7e880008190a6ad7e06e5d03007 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ebd1016481909b8ba3b047a47145 completed Feb. 28, 2026, 1:21 p.m.
PD Predicate disambiguation batch_69a2e95dbb208190b277fc5352a4ee84 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.