Triple
T31898379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | correspondence principle |
E814351
|
entity |
| Predicate | relatesTheory |
P136097
|
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: [correspondence principle, relatesTheory, quantum mechanics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatesTheory Context triple: [correspondence principle, relatesTheory, quantum mechanics]
-
A.
reflectsTheoryOf
Indicates that one entity embodies, expresses, or is based on the theoretical framework, principles, or assumptions developed by another entity.
-
B.
relatedTheorem
Indicates that one theorem is connected to another through a logical, thematic, or derivational relationship.
-
C.
followsTheoryOf
Indicates that one entity adheres to, is based on, or is guided by the theoretical framework or principles established by another entity.
-
D.
coversTheory
chosen
Indicates that one entity includes, addresses, or explains the theoretical concepts associated with another entity.
-
E.
presentsTheory
Indicates that one entity formally puts forward or explains a theory to another entity or audience.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:59 p.m.