Triple
T3411709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomonaga–Schwinger equation |
E71910
|
entity |
| Predicate | formulation |
P9767
|
FINISHED |
| Object | covariant canonical formalism |
—
|
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: covariant canonical formalism | Statement: [Tomonaga–Schwinger equation, formulation, covariant canonical formalism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formulation Context triple: [Tomonaga–Schwinger equation, formulation, covariant canonical formalism]
-
A.
hasFormulation
Indicates that one entity is expressed, prepared, or configured in a particular form or composition defined by another entity.
-
B.
coFormulated
Indicates that two or more entities were jointly formulated, designed, or created together as part of the same process or product.
-
C.
standardFormulation
Indicates that something is expressed or represented in a conventional, officially accepted, or commonly used form or version.
-
D.
formulatedIn
chosen
Indicates that something was created, developed, or expressed within a particular context, place, or framework.
-
E.
implementationForm
Indicates the specific manner, format, or method by which something is implemented or realized in practice.
- 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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb90a76288190b92ef3b26638cd47 |
completed | March 8, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.