Triple
T378973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fokker–Planck equation |
E8633
|
entity |
| Predicate | canBeWrittenIn |
P12679
|
FINISHED |
| Object | conservation form |
—
|
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: conservation form | Statement: [Fokker–Planck equation, canBeWrittenIn, conservation form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeWrittenIn Context triple: [Fokker–Planck equation, canBeWrittenIn, conservation form]
-
A.
areWrittenOn
Indicates that one entity serves as a surface or medium on which another entity is inscribed, recorded, or written.
-
B.
wrote
Indicates that an entity is the author or creator of a written work involving another entity.
-
C.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
D.
writtenForm
Indicates that one entity is the textual or orthographic representation (spelling or written version) of another entity.
-
E.
writingSystem
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a2eae0bd7081908197bbf5c55fe647 |
completed | Feb. 28, 2026, 1:17 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.