Triple
T24231858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goldberger–Treiman relation |
E601754
|
entity |
| Predicate | derivedInFramework |
P909
|
FINISHED |
| Object | chiral SU(2) × SU(2) symmetry |
—
|
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: chiral SU(2) × SU(2) symmetry | Statement: [Goldberger–Treiman relation, derivedInFramework, chiral SU(2) × SU(2) symmetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivedInFramework Context triple: [Goldberger–Treiman relation, derivedInFramework, chiral SU(2) × SU(2) symmetry]
-
A.
isPartOfFramework
Indicates that one entity functions as a component, module, or element within a larger structured framework or system.
-
B.
parentFramework
Indicates that one framework serves as the higher-level or containing framework from which another framework is derived, organized, or structured.
-
C.
derivedFrom
chosen
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
D.
appliesFramework
Indicates that one entity uses or implements a particular framework in relation to another entity or context.
-
E.
adoptedFrameworkType
Indicates that one entity has chosen and is using a particular framework type as its adopted standard or approach.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287e3de908190917a5bf66d9df5c9 |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:02 a.m.