Triple
T6832843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaussian surface |
E157379
|
entity |
| Predicate | typicalSymmetry |
P12998
|
FINISHED |
| Object | spherical 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: spherical symmetry | Statement: [Gaussian surface, typicalSymmetry, spherical symmetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSymmetry Context triple: [Gaussian surface, typicalSymmetry, spherical symmetry]
-
A.
localSymmetry
Indicates that an entity exhibits symmetry within a localized region or subset of its structure, rather than across its entire extent.
-
B.
testsSymmetry
Indicates that one entity evaluates or verifies whether a relationship or property holds identically in both directions between two entities.
-
C.
typicalSymbol
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
-
D.
usesSymmetryGroup
chosen
Indicates that one entity employs or is based on a particular symmetry group in its structure, behavior, or formulation.
-
E.
typicalTopology
Indicates the usual or most common network or structural arrangement that characterizes how the related entities are organized or interconnected.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62b1e8c8190a81d91191a54b073 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.