Triple
T15791380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pareto distribution |
E382868
|
entity |
| Predicate | parameterConstraint |
P58313
|
FINISHED |
| Object | α > 0 |
—
|
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: α > 0 | Statement: [Pareto distribution, parameterConstraint, α > 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parameterConstraint Context triple: [Pareto distribution, parameterConstraint, α > 0]
-
A.
constrainedBy
Indicates that one entity’s state, behavior, or possibilities are limited, restricted, or governed by another entity.
-
B.
designedToConstrain
Indicates that one entity is intentionally created or configured to limit, restrict, or control the behavior, range, or properties of another entity.
-
C.
hasFormalConstraint
chosen
Indicates that an entity is governed or restricted by an explicitly defined formal rule, condition, or limitation.
-
D.
massConstraintType
Indicates the specific kind or category of restriction applied to an entity’s mass within a system or model.
-
E.
parameter
Indicates that one entity serves as a parameter or argument that configures, constrains, or influences the behavior or outcome of another entity or process.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d819c881908bc43a6124a1bb2e |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.