Triple
T22842380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirac quantization condition |
E566115
|
entity |
| Predicate | appliesToTheory |
P1129
|
FINISHED |
| Object | quantum mechanics |
—
|
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: quantum mechanics | Statement: [Dirac quantization condition, appliesToTheory, quantum mechanics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToTheory Context triple: [Dirac quantization condition, appliesToTheory, quantum mechanics]
-
A.
appliesTheory
Indicates that an entity uses or implements a particular theory in analyzing, explaining, or addressing something.
-
B.
hasTheory
Indicates that an entity possesses, is associated with, or is characterized by a particular theory.
-
C.
appliesTo
chosen
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
D.
followsTheoryOf
Indicates that one entity adheres to, is based on, or is guided by the theoretical framework or principles established by another entity.
-
E.
reflectsTheoryOf
Indicates that one entity embodies, expresses, or is based on the theoretical framework, principles, or assumptions developed by another entity.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e855abc8190b9cf8cc515090a7f |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:35 p.m.