Triple
T35184059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Low’s soft-photon theorem |
E1015933
|
entity |
| Predicate | typeOfSoftTheorem |
P203516
|
FINISHED |
| Object | leading soft-photon theorem |
—
|
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: leading soft-photon theorem | Statement: [Low’s soft-photon theorem, typeOfSoftTheorem, leading soft-photon theorem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSoftTheorem Context triple: [Low’s soft-photon theorem, typeOfSoftTheorem, leading soft-photon theorem]
-
A.
theoryType
Indicates the classification relationship that specifies what type or category of theory an entity belongs to.
-
B.
isSoft
Indicates that one entity has a soft or yielding texture or consistency when touched or pressed.
-
C.
typeOfRules
Indicates that one entity specifies or categorizes the kind or category of rules that apply to or are associated with another entity.
-
D.
InType
Indicates that an entity belongs to, is categorized under, or is an instance of a specified type or class.
-
E.
SOType
Indicates the specific type or category of a sales order associated with an entity or transaction.
- F. None of above. chosen
Provenance (4 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a019579463c8190b51e39183b57bbaf |
completed | May 11, 2026, 8:38 a.m. |
| PD | Predicate disambiguation | batch_6a0192d309488190a3d86c93e7138c77 |
completed | May 11, 2026, 8:26 a.m. |
| PDg | Predicate description generation | batch_6a019578545c8190964a8b9087d3a46a |
completed | May 11, 2026, 8:38 a.m. |
Created at: May 3, 2026, 4:02 p.m.