Triple
T23202163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Floquet systems |
E580346
|
entity |
| Predicate | analyzedInTermsOf |
P78878
|
FINISHED |
| Object | Floquet modes |
—
|
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: Floquet modes | Statement: [Floquet systems, analyzedInTermsOf, Floquet modes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: analyzedInTermsOf Context triple: [Floquet systems, analyzedInTermsOf, Floquet modes]
-
A.
analyzes
Indicates that one entity systematically examines or evaluates another entity to understand its nature, structure, or components.
-
B.
formulatedInTermsOf
chosen
Indicates that one concept, statement, or representation is expressed, defined, or described using the language, framework, or components of another.
-
C.
oftenAnalyzedIn
Indicates that something is frequently examined, studied, or evaluated within a particular context, field, or framework.
-
D.
analyzesRelationBetween
Indicates a relationship in which one entity examines, interprets, or evaluates the connection or interaction between two or more other entities.
-
E.
analysisType
Indicates the specific kind or category of analysis being applied or performed in relation to an entity or dataset.
- 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907a8bb48190846802a24d33bccf |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:06 p.m.