Triple
T100400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCS theory of superconductivity |
E2026
|
entity |
| Predicate | framework |
P2450
|
FINISHED |
| Object | second quantization |
—
|
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: second quantization | Statement: [BCS theory of superconductivity, framework, second quantization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: framework Context triple: [BCS theory of superconductivity, framework, second quantization]
-
A.
currentFrameworkBasedOn
chosen
Indicates that the current framework is derived from, built upon, or structured according to another underlying framework.
-
B.
front
Indicates that one entity is located directly before or facing another entity along a primary viewing or movement direction.
-
C.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
D.
frontType
Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
-
E.
configuration
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a253b95d4c81909d1f2bc37e799c44 |
completed | Feb. 28, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69a24ebfc5a88190bdd1653b9fa541fe |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.