Triple

T19749937
Position Surface form Disambiguated ID Type / Status
Subject PolarDB E474348 entity
Predicate scalingType P79847 FINISHED
Object horizontal scaling 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: horizontal scaling | Statement: [PolarDB, scalingType, horizontal scaling]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: scalingType
Context triple: [PolarDB, scalingType, horizontal scaling]
  • A. scalingProperty
    Indicates how a quantity or behavior changes in proportion to changes in another variable, typically under resizing or rescaling conditions.
  • B. autoscalingType chosen
    Indicates the method or strategy by which a system automatically adjusts its resource capacity (such as scaling up or down) in response to changing demand or conditions.
  • C. scaleDefinition
    Indicates that an entity specifies the parameters, structure, or measurement system used to define a particular scale.
  • D. scaleProperty
    Indicates that one entity defines or modifies the scale, magnitude, or proportional sizing used to interpret or represent a property of another entity.
  • E. scaleFunction
    Indicates a relationship where one entity defines how another entity’s values are proportionally adjusted or transformed according to a scaling rule or factor.
  • 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_69d8e51940a0819087bd2996f98da668 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6529875688190952af476aa5be492 completed April 20, 2026, 4:21 p.m.
PD Predicate disambiguation batch_69e5305016e08190b9561a96baecb0b8 completed April 19, 2026, 7:43 p.m.
Created at: April 10, 2026, 1:47 p.m.