Triple
T22666625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poisson process |
E559807
|
entity |
| Predicate | hasCountingProcessNotation |
P149163
|
FINISHED |
| Object | N(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: N(t) | Statement: [Poisson process, hasCountingProcessNotation, N(t)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountingProcessNotation Context triple: [Poisson process, hasCountingProcessNotation, N(t)]
-
A.
hasCountingPeriod
Indicates that there is a defined time span or interval over which occurrences, quantities, or measurements related to an entity are counted or aggregated.
-
B.
hasCountingDirection
Indicates the direction or order in which counting or enumeration proceeds between related entities.
-
C.
numberOfCounts
Indicates the total quantity or tally of discrete occurrences, items, or instances associated with an entity or event.
-
D.
isCountedAs
Indicates that one entity is treated or included as part of the tally, total, or quantitative assessment of another entity.
-
E.
hasNumberingRole
Indicates that an entity holds a specific role or responsibility related to assigning, managing, or using numbers within a given context.
- 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_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. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:09 p.m.