Triple

T31993018
Position Surface form Disambiguated ID Type / Status
Subject OpenShift worker nodes E816918 entity
Predicate scaledBy P173097 FINISHED
Object cluster administrators 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: cluster administrators | Statement: [OpenShift worker nodes, scaledBy, cluster administrators]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: scaledBy
Context triple: [OpenShift worker nodes, scaledBy, cluster administrators]
  • A. scalesBy
    Indicates a relationship where one quantity, object, or representation is proportionally enlarged or reduced relative to another by a specific scaling factor.
  • B. similarScaleTo
    Indicates that two entities have comparable magnitude, size, or extent along a given dimension or measurement scale.
  • C. scaleProperty
    Indicates that one entity defines or modifies the scale, magnitude, or proportional sizing used to interpret or represent a property of another entity.
  • D. associatedScale
    Indicates that one entity is linked or connected to a particular scale used to measure, classify, or evaluate it.
  • E. wasScaledFor
    Indicates that something was adjusted in size, capacity, or extent to suit a particular context, requirement, or target.
  • 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_69f348f8002081909a3588758ba94afb completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b3badf8481909377856a516a982b completed May 3, 2026, 2:32 a.m.
PD Predicate disambiguation batch_69f6b151ad008190836c1bcdec503ce2 completed May 3, 2026, 2:22 a.m.
PDg Predicate description generation batch_69f6b21da77081908c5c015c4606d344 completed May 3, 2026, 2:25 a.m.
Created at: May 1, 2026, 12:13 a.m.