Triple

T29655016
Position Surface form Disambiguated ID Type / Status
Subject Colossus E750240 entity
Predicate controlCost P192771 FINISHED
Object high supply cost 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: high supply cost | Statement: [Colossus, controlCost, high supply cost]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: controlCost
Context triple: [Colossus, controlCost, high supply cost]
  • A. controlInnovation
    Indicates that one entity directs, regulates, or significantly influences the innovation activities or outcomes of another entity.
  • B. exportControl
    Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
  • C. controlled
    Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
  • D. controlParameter
    Indicates that one entity functions as a parameter that governs, tunes, or constrains the behavior or operation of another entity.
  • E. controlMeasure
    Indicates a relationship where one entity implements or applies a method, action, or mechanism to regulate, mitigate, or manage a risk, process, or condition associated with another entity.
  • 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_69f0d6226fe881908819197c9ef9ee04 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69fd2a215d6c8190a1a428ccaee603f1 completed May 8, 2026, 12:11 a.m.
PD Predicate disambiguation batch_69fd28ef19688190bb8370f2812a43e7 completed May 8, 2026, 12:06 a.m.
PDg Predicate description generation batch_69fd2a2095f88190bfcbcb2973516ffc completed May 8, 2026, 12:11 a.m.
Created at: April 28, 2026, 6:54 p.m.