Triple
T2716848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Itô’s lemma |
E59984
|
entity |
| Predicate | isFormulatedIn |
P9767
|
FINISHED |
| Object | continuous 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: continuous time | Statement: [Itô’s lemma, isFormulatedIn, continuous time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFormulatedIn Context triple: [Itô’s lemma, isFormulatedIn, continuous time]
-
A.
formulatedIn
chosen
Indicates that something was created, developed, or expressed within a particular context, place, or framework.
-
B.
hasFormulation
Indicates that one entity is expressed, prepared, or configured in a particular form or composition defined by another entity.
-
C.
isFormalizedBy
Indicates that something is given a defined, structured, or official form through a specific method, process, or representation.
-
D.
formulatedInYear
Indicates the specific calendar year in which something was originally created, devised, or formally established.
-
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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda964d4881908179b2a1b16411e4 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8240920819087a812d816a55edb |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.