Triple
T15791352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pareto distribution |
E382868
|
entity |
| Predicate | meanExistsIf |
P67472
|
FINISHED |
| Object | α > 1 |
—
|
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: α > 1 | Statement: [Pareto distribution, meanExistsIf, α > 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meanExistsIf Context triple: [Pareto distribution, meanExistsIf, α > 1]
-
A.
existsIf
chosen
Indicates that the existence or validity of one entity or condition depends on the presence or truth of another specified condition.
-
B.
hasExistentiale
Indicates that an entity possesses or is associated with an existential characteristic, condition, or mode of being.
-
C.
existsFor
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
-
D.
hasExits
Indicates that an entity provides one or more ways out or routes leading from it to other locations or states.
-
E.
meetsInPresenceOf
Indicates that two or more entities meet or interact while another specified entity is present as a witness, chaperone, or contextual participant.
- 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.