Triple

T16238520
Position Surface form Disambiguated ID Type / Status
Subject Combustion Engineering PWR E394178 entity
Predicate primaryLoops P122285 FINISHED
Object two-loop configuration 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: two-loop configuration | Statement: [Combustion Engineering PWR, primaryLoops, two-loop configuration]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryLoops
Context triple: [Combustion Engineering PWR, primaryLoops, two-loop configuration]
  • A. primaryCircuits
    Indicates that one entity functions as a main or principal circuit in relation to another entity.
  • B. primaryCircuit
    Indicates that one entity functions as the main or first-stage electrical path or loop in relation to another system or circuit.
  • C. primaryConnections
    Indicates that there exists a main or most significant relationship or linkage between entities, distinguishing these connections from secondary or peripheral ones.
  • D. primaryFront
    Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
  • E. primaryFor
    Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
  • 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_69d87f2171208190951025e526947816 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2455c7a3c81909e3b42edf03be43e completed April 17, 2026, 2:36 p.m.
PD Predicate disambiguation batch_69e219ee6f6481909663b388dc99770a completed April 17, 2026, 11:30 a.m.
PDg Predicate description generation batch_69e21e55a2388190b29a045a8c608ba4 completed April 17, 2026, 11:49 a.m.
Created at: April 10, 2026, 5:04 a.m.