Triple
T378962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fokker–Planck equation |
E8633
|
entity |
| Predicate | timeDependent |
P9753
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fokker–Planck equation, timeDependent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeDependent Context triple: [Fokker–Planck equation, timeDependent, yes]
-
A.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
C.
timescale
Indicates the temporal scale or duration over which a process, relationship, or effect occurs or is evaluated.
-
D.
timeDescribedAs
Indicates that a specific time or temporal interval is characterized, labeled, or expressed using a particular description or representation.
-
E.
timeContinuousOrDiscrete
chosen
Indicates whether the time dimension in a given context is modeled as a continuous flow or as discrete, separate time points.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2974988190a1d6316cbb5159c8 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e964d4b481909290e474b0341e3c |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.