Triple
T22666611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poisson process |
E559807
|
entity |
| Predicate | hasMeanIncrementOnInterval |
P63472
|
FINISHED |
| Object | λt for interval length t |
—
|
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: λt for interval length t | Statement: [Poisson process, hasMeanIncrementOnInterval, λt for interval length t]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeanIncrementOnInterval Context triple: [Poisson process, hasMeanIncrementOnInterval, λt for interval length t]
-
A.
hasIncrement
Indicates that one value or state increases by a specified step or amount relative to another.
-
B.
hasInterval
chosen
Indicates that something is associated with a specific span or range between two points in time, space, or value.
-
C.
isIncremental
Indicates that something progresses or changes in small, successive steps or increases over time.
-
D.
usesIncrement
Indicates that one entity applies or relies on an increment operation or incremental value derived from another entity.
-
E.
hasBaseInterval
Indicates that one entity has a fundamental or reference interval that serves as the base measurement or range for another related quantity or structure.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781c2c808190baf6964ca1eced6f |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:09 p.m.