Triple
T36467802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyson Brownian motion |
E898465
|
entity |
| Predicate | hasContinuousTimeParameter |
P9753
|
FINISHED |
| Object | time |
—
|
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: time | Statement: [Dyson Brownian motion, hasContinuousTimeParameter, time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContinuousTimeParameter Context triple: [Dyson Brownian motion, hasContinuousTimeParameter, time]
-
A.
isContinuous
Indicates that a function, process, or relationship changes smoothly without abrupt jumps or breaks over its domain.
-
B.
timeContinuousOrDiscrete
chosen
Indicates whether the time dimension in a given context is modeled as a continuous flow or as discrete, separate time points.
-
C.
isContinuously
Indicates that an action, state, or relationship persists without interruption over a period of time.
-
D.
canBeContinuous
Indicates that something has the potential to occur, exist, or be maintained without interruption over a continuous range or period.
-
E.
isContinuouslyAvailable
Indicates that the subject remains accessible or in operation without interruption over a period of time.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.