Triple
T25097477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laplace distribution |
E628628
|
entity |
| Predicate | supportUpperBound |
P14327
|
FINISHED |
| Object | +∞ |
—
|
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: +∞ | Statement: [Laplace distribution, supportUpperBound, +∞]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportUpperBound Context triple: [Laplace distribution, supportUpperBound, +∞]
-
A.
supportLowerBound
Indicates that one entity provides or defines a minimum level or lower limit of support for another entity or condition.
-
B.
includesUpperBound
Indicates that the specified range or interval contains and counts its upper limit value as part of the set.
-
C.
supportsReach
Indicates that one entity enables, facilitates, or maintains the ability of another entity to extend its influence, access, or coverage to additional targets or areas.
-
D.
isUpperBoundFor
chosen
Indicates that one value is greater than or equal to every element in a given set or collection, serving as an upper limit for them.
-
E.
supportedAfter
Indicates that one entity provided support to another only after a specified event, time, or condition had occurred.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 18, 2026, 6:25 a.m.