Triple
T35335344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lévy processes |
E1020434
|
entity |
| Predicate | indexSet |
P183036
|
FINISHED |
| Object | nonnegative 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: nonnegative real numbers | Statement: [Lévy processes, indexSet, nonnegative real numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indexSet Context triple: [Lévy processes, indexSet, nonnegative real numbers]
-
A.
indexStructure
Indicates that one entity serves as an index or organizational framework that structures, arranges, or provides access to another entity or set of entities.
-
B.
indexType
Indicates the classification or category of an index associated with an entity or structure.
-
C.
indexed
Indicates that one entity is organized, recorded, or referenced within a systematic index or catalog relative to another entity.
-
D.
indexUsedBy
Indicates that a particular index is utilized or referenced by another entity, such as a query, process, or data structure.
-
E.
indexSize
Indicates the size or magnitude of an index associated with an entity, such as its length, capacity, or storage footprint.
- 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f795b5228c8190adb5bf86e581f70c |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f79527c7bc8190a69d87bec01f65c8 |
completed | May 3, 2026, 6:34 p.m. |
Created at: May 3, 2026, 4:03 p.m.