Triple
T4896336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greek cross |
E109687
|
entity |
| Predicate | hasSymmetryType |
P60479
|
FINISHED |
| Object | bilateral 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: bilateral symmetry | Statement: [Greek cross, hasSymmetryType, bilateral symmetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSymmetryType Context triple: [Greek cross, hasSymmetryType, bilateral symmetry]
-
A.
usesSymmetryGroup
Indicates that one entity employs or is based on a particular symmetry group in its structure, behavior, or formulation.
-
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.
hasSymmetryGroupOrder
Indicates that an entity possesses a symmetry group whose total number of distinct symmetry operations equals the given order.
-
D.
testsSymmetry
Indicates that one entity evaluates or verifies whether a relationship or property holds identically in both directions between two entities.
-
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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffabccc81909115ece1b04e2061 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2e7b5c8190b8bf9d616dfa24f0 |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6ff731188190a9903602122d4ff9 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:28 p.m.