Triple
T6272127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | time crystals |
E140560
|
entity |
| Predicate | break |
P69083
|
FINISHED |
| Object | time-translation 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: time-translation symmetry | Statement: [time crystals, break, time-translation symmetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: break Context triple: [time crystals, break, time-translation symmetry]
-
A.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
B.
breakType
Indicates the specific kind or category of break or interruption that occurs in a process, activity, or sequence.
-
C.
broken
Indicates that an entity is damaged or no longer functioning as intended, often as the result of some prior action or event.
-
D.
brokenUp
Indicates that a previously existing romantic or close relationship between two entities has ended.
-
E.
breakthrough
Indicates a significant and often sudden advance or discovery that overcomes a major obstacle in a process, field, or endeavor.
- 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_69c008cabc4081909723e2547c9d6cc0 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063bca5488190b9da3c037cfc7953 |
completed | March 22, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69c05606fb50819082d1a5a91e5030b6 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c965ac8190b938502fa8c74e1b |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:25 p.m.