Triple
T378971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fokker–Planck equation |
E8633
|
entity |
| Predicate | hasSolutionType |
P4453
|
FINISHED |
| Object | probability density function over state space |
—
|
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: probability density function over state space | Statement: [Fokker–Planck equation, hasSolutionType, probability density function over state space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSolutionType Context triple: [Fokker–Planck equation, hasSolutionType, probability density function over state space]
-
A.
admitsSolution
Indicates that a problem, system, or situation allows for or possesses at least one valid solution.
-
B.
solutionType
chosen
Indicates the specific category or kind of solution associated with an entity or problem.
-
C.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
D.
hasSingularityType
Indicates that an entity possesses or is characterized by a specific type or category of singularity.
-
E.
hasFormulationType
Indicates the specific way something is physically prepared or presented, such as its dosage form, composition, or delivery format.
- 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.