Triple
T6272144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | time crystals |
E140560
|
entity |
| Predicate | wereFirstRealizedInSystem |
P1588
|
FINISHED |
| Object | trapped ions |
—
|
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: trapped ions | Statement: [time crystals, wereFirstRealizedInSystem, trapped ions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wereFirstRealizedInSystem Context triple: [time crystals, wereFirstRealizedInSystem, trapped ions]
-
A.
wasFirstObservedIn
Indicates that an entity was initially noticed, recorded, or detected at a particular time or place.
-
B.
firstDemonstrated
chosen
Indicates that one entity was the earliest to show, prove, or exemplify a particular concept, method, or capability in relation to another entity or context.
-
C.
introducedInSystem
Indicates that an entity was first added, implemented, or made available within a particular system.
-
D.
historicallyImplementedIn
Indicates that an action, practice, or system was carried out or put into effect in a particular place or context during a past historical period.
-
E.
firstAppearedAt
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
- 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.