Triple
T22666596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poisson process |
E559807
|
entity |
| Predicate | hasIndexSet |
P149159
|
FINISHED |
| Object | non‑negative real numbers |
—
|
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: non‑negative real numbers | Statement: [Poisson process, hasIndexSet, non‑negative real numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndexSet Context triple: [Poisson process, hasIndexSet, non‑negative real numbers]
-
A.
hasIndex
Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
-
B.
hasIndexType
Indicates that an entity is associated with a particular type or category of index used to organize, reference, or access it.
-
C.
hasListedIndex
Indicates that an entity is associated with a specific index on which it is officially listed or traded.
-
D.
hasIndexMembership
Indicates that an entity is included as a member or constituent within a specified index or indexed collection.
-
E.
hasBaseIndex
Indicates that one entity serves as the reference or starting index from which another entity’s position, offset, or ordering is calculated.
- 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.