Triple
T478152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eliashberg theory |
E9105
|
entity |
| Predicate | frameworkType |
P11925
|
FINISHED |
| Object | self-consistent integral equations |
—
|
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: self-consistent integral equations | Statement: [Eliashberg theory, frameworkType, self-consistent integral equations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frameworkType Context triple: [Eliashberg theory, frameworkType, self-consistent integral equations]
-
A.
frameworkFor
Indicates that one entity serves as a supporting structure, system, or basis that organizes, guides, or enables the development or functioning of another entity.
-
B.
frameType
chosen
Indicates the specific structural or categorical kind of frame associated with an entity or relation.
-
C.
currentFrameworkBasedOn
Indicates that the current framework is derived from, built upon, or structured according to another underlying framework.
-
D.
webFramework
Indicates that one entity is a web framework used to build or support web applications for the other entity.
-
E.
appliesFramework
Indicates that one entity uses or implements a particular framework in relation to another entity or context.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f03f3fbc81909af6e4496d5e6c2a |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf017548190ae38ff3314a1ffa3 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.