Triple
T1889406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BASE experiment |
E41834
|
entity |
| Predicate | testsSymmetry |
P33072
|
FINISHED |
| Object | CPT 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: CPT symmetry | Statement: [BASE experiment, testsSymmetry, CPT symmetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testsSymmetry Context triple: [BASE experiment, testsSymmetry, CPT symmetry]
-
A.
isSymmetricAbout
Indicates that one entity is a mirror image of another with respect to a specified axis, point, or plane of symmetry.
-
B.
isSymmetric
Indicates that a relationship holds in both directions between two entities, so if it applies from A to B, it also applies from B to A.
-
C.
usesSymmetryGroup
Indicates that one entity employs or is based on a particular symmetry group in its structure, behavior, or formulation.
-
D.
localSymmetry
Indicates that an entity exhibits symmetry within a localized region or subset of its structure, rather than across its entire extent.
-
E.
isMaximallySymmetric
Indicates that the subject exhibits the highest possible degree of symmetry allowed by the relevant structure, constraints, or context.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb142e41881908fc7335673a9dec3 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb11bfd2c8190a805372589f73238 |
completed | March 7, 2026, 5:01 a.m. |
Created at: March 4, 2026, 7:34 p.m.