Triple
T34542355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyno |
E886835
|
entity |
| Predicate | scaledVia |
P179292
|
FINISHED |
| Object | dyno formation |
—
|
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: dyno formation | Statement: [Dyno, scaledVia, dyno formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scaledVia Context triple: [Dyno, scaledVia, dyno formation]
-
A.
scaledBy
Indicates that one quantity, object, or value is obtained by multiplying another by a specific factor or scale.
-
B.
scalingProperty
Indicates how a quantity or behavior changes in proportion to changes in another variable, typically under resizing or rescaling conditions.
-
C.
scaleUsed
Indicates that a particular scale or measurement system is employed in performing, recording, or interpreting an action or relationship.
-
D.
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.
-
E.
scaleOptimizedFor
Indicates that something has been adjusted or configured to operate most efficiently at a particular size, level, or magnitude.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: May 1, 2026, 2:02 a.m.