Triple
T5877569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwinger model |
E130663
|
entity |
| Predicate | isExactlySolvable |
P67394
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Schwinger model, isExactlySolvable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExactlySolvable Context triple: [Schwinger model, isExactlySolvable, true]
-
A.
isSolutionOf
Indicates that one entity is a correct answer or satisfies the conditions of a given problem, equation, or task.
-
B.
admitsSolution
Indicates that a problem, system, or situation allows for or possesses at least one valid solution.
-
C.
hasClosedForm
Indicates that a mathematical expression, function, or solution can be written in a finite, explicit form using a standard set of operations and well-known functions.
-
D.
isVacuumSolution
Indicates that a spacetime metric satisfies Einstein’s field equations in the absence of matter or non-gravitational energy (i.e., the stress-energy tensor is zero).
-
E.
providesSolutionFor
Indicates that one entity offers or supplies a remedy, answer, or resolution to a problem, need, or issue associated with 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c0432f06fc8190bc047d52ffc30d59 |
completed | March 22, 2026, 7:29 p.m. |
Created at: March 22, 2026, 3:57 p.m.