Triple
T32413993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | API Apps |
E828294
|
entity |
| Predicate | supportsScaling |
P127910
|
FINISHED |
| Object | manual 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: manual scaling | Statement: [API Apps, supportsScaling, manual scaling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsScaling Context triple: [API Apps, supportsScaling, manual scaling]
-
A.
supportsScalingDirection
Indicates that one entity enables or is compatible with a particular direction or mode of scaling (such as scaling up, scaling down, or scaling out) of another entity.
-
B.
supportScale
chosen
Indicates that one entity enables or accommodates the other’s ability to grow or operate effectively at larger size, capacity, or load.
-
C.
isScalable
Indicates that something can handle increasing amounts of work, users, or data without a proportional loss of performance or efficiency.
-
D.
requiresFeatureScaling
Indicates that applying feature scaling is a necessary preprocessing step for the associated data or model.
-
E.
supportsContentsScale
Indicates that an object can adjust its content rendering to match a specified display or screen scale 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:53 a.m.