Triple

T36489578
Position Surface form Disambiguated ID Type / Status
Subject ENAS E899017 entity
Predicate superNetworkType P192880 FINISHED
Object directed acyclic graph 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: directed acyclic graph | Statement: [ENAS, superNetworkType, directed acyclic graph]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: superNetworkType
Context triple: [ENAS, superNetworkType, directed acyclic graph]
  • A. networkType
    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. providesNetworkType
    Indicates that one entity supplies or specifies the type of network associated with another entity.
  • C. networkTypePromoted
    Indicates that a particular type of network has been elevated, highlighted, or given priority status within a system or context.
  • D. supportedNetwork
    Indicates that one entity (such as a device, service, or application) is compatible with, operates on, or is designed to work over a specified network or type of network.
  • E. routeNetworkType
    Indicates the specific kind of transportation or communication network to which a route belongs (e.g., road, rail, or air).
  • 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_69f76e5ad4588190bdbce60c52fbb785 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fd2cf39b0c8190811b8a6fa9410560 completed May 8, 2026, 12:23 a.m.
PD Predicate disambiguation batch_69fd2ad8dd988190a9899701ba00d917 completed May 8, 2026, 12:14 a.m.
PDg Predicate description generation batch_69fd2cf29f808190856ab1d43a51d5c7 completed May 8, 2026, 12:23 a.m.
Created at: May 3, 2026, 4:10 p.m.