Triple
T9937979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | photon |
E194003
|
entity |
| Predicate | obeysTheory |
P79559
|
FINISHED |
| Object | quantum electrodynamics |
—
|
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 electrodynamics | Statement: [photon, obeysTheory, quantum electrodynamics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obeysTheory Context triple: [photon, obeysTheory, quantum electrodynamics]
-
A.
followsTheoryOf
chosen
Indicates that one entity adheres to, is based on, or is guided by the theoretical framework or principles established by another entity.
-
B.
obeysLaw
Indicates that an entity follows, complies with, or acts in accordance with a specified law or set of laws.
-
C.
obeysStatistics
Indicates that one entity’s behavior or outcomes conform to, follow, or are governed by statistical laws or patterns.
-
D.
governingTheory
Indicates that one entity serves as the primary theoretical framework or principle that explains, constrains, or directs the behavior, interpretation, or operation of another entity.
-
E.
appliesTheory
Indicates that an entity uses or implements a particular theory in analyzing, explaining, or addressing something.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5e64760819094f599f158d32f33 |
completed | April 2, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:44 p.m.