Triple
T6272167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | time crystals |
E140560
|
entity |
| Predicate | areDiscussedIn |
P33880
|
FINISHED |
| Object | quantum thermodynamics |
—
|
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: quantum thermodynamics | Statement: [time crystals, areDiscussedIn, quantum thermodynamics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areDiscussedIn Context triple: [time crystals, areDiscussedIn, quantum thermodynamics]
-
A.
frequentlyDiscussedIn
Indicates that a topic, subject, or entity is often the focus of conversation, debate, or mention within a particular context or medium.
-
B.
containsDiscussionOf
chosen
Indicates that one entity includes or features a discussion, treatment, or consideration of another entity as a topic or subject.
-
C.
discussed
Indicates that one entity talked about, examined, or debated a topic, issue, or other entity with someone else.
-
D.
debatedWithin
Indicates that something is discussed or argued about within a particular group, context, or domain.
-
E.
influencedDiscussionOf
Indicates that one entity had an effect on the way another entity was discussed, framed, or debated.
- 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_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. |
Created at: March 22, 2026, 4:25 p.m.