Triple
T100603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feynman–Kac formula |
E2031
|
entity |
| Predicate | generalizedBy |
P2372
|
FINISHED |
| Object | nonlinear Feynman–Kac formulas |
—
|
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: nonlinear Feynman–Kac formulas | Statement: [Feynman–Kac formula, generalizedBy, nonlinear Feynman–Kac formulas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generalizedBy Context triple: [Feynman–Kac formula, generalizedBy, nonlinear Feynman–Kac formulas]
-
A.
generalizationOf
chosen
Indicates that one entity represents a broader, more general concept or category that subsumes or abstracts over another, more specific entity.
-
B.
grantedBy
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
-
C.
standardizedBy
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
-
D.
formedBy
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
-
E.
derivedFrom
Indicates that one entity originates, is obtained, or is developed from another source entity.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24ff1a8cc8190843d4c6807cebd09 |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24ec0a97c81909a7c98962f40b2ed |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.