Triple
T6397009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AdS isometry group SO(2,d) |
E143965
|
entity |
| Predicate | isGlobalSymmetryOf |
P12998
|
FINISHED |
| Object | AdS_{d+1} background |
—
|
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: AdS_{d+1} background | Statement: [AdS isometry group SO(2,d), isGlobalSymmetryOf, AdS_{d+1} background]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGlobalSymmetryOf
Context triple: [AdS isometry group SO(2,d), isGlobalSymmetryOf, AdS_{d+1} background]
-
A.
usesSymmetryGroup
chosen
Indicates that one entity employs or is based on a particular symmetry group in its structure, behavior, or formulation.
-
B.
isMaximallySymmetric
Indicates that the subject exhibits the highest possible degree of symmetry allowed by the relevant structure, constraints, or context.
-
C.
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.
-
D.
hasSymmetryType
Indicates that one entity possesses a specific kind or pattern of symmetry characterized or classified by the other entity.
-
E.
hasSymmetryGroupOrder
Indicates that an entity possesses a symmetry group whose total number of distinct symmetry operations equals the given order.
- 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_69c008db906c819096f3597d55d95432 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c068953968819083a94f5de3e11819 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:35 p.m.