Triple
T25097476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laplace distribution |
E628628
|
entity |
| Predicate | supportLowerBound |
P167705
|
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, supportLowerBound, -∞]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportLowerBound Context triple: [Laplace distribution, supportLowerBound, -∞]
-
A.
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.
-
B.
supportedFrom
Indicates that one entity provides backing, assistance, or justification for another entity, often serving as the source or basis of that support.
-
C.
supportedAfter
Indicates that one entity provided support to another only after a specified event, time, or condition had occurred.
-
D.
supportedRight
Indicates that one entity endorsed, upheld, or actively backed the right or entitlement held by another entity.
-
E.
supportScale
Indicates that one entity enables or accommodates the other’s ability to grow or operate effectively at larger size, capacity, or load.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 18, 2026, 6:25 a.m.