Triple
T11961972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brownian filtration |
E284689
|
entity |
| Predicate | timeIndexedBy |
P30229
|
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: [Brownian filtration, timeIndexedBy, nonnegative real numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeIndexedBy Context triple: [Brownian filtration, timeIndexedBy, nonnegative real numbers]
-
A.
timeIndexed
chosen
Indicates that the relationship or property it connects is associated with, or valid during, a specific time or time interval.
-
B.
timeNamed
Indicates that a specific time or temporal interval is referred to or identified by a particular name or label.
-
C.
timeInSeries
Indicates that one temporal value occurs within the duration or sequence span defined by another in a series.
-
D.
timeCoordinateType
Indicates the specific temporal reference system or framework used to define and interpret time coordinates for an event or entity.
-
E.
timeRecorded
Indicates that a specific point or period in time has been captured and stored as associated with an event, action, or state.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037848f481908276716675464464 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.