Triple
T2173588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermi liquid theory |
E48476
|
entity |
| Predicate | validRegime |
P9768
|
FINISHED |
| Object | low temperatures |
—
|
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: low temperatures | Statement: [Fermi liquid theory, validRegime, low temperatures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: validRegime Context triple: [Fermi liquid theory, validRegime, low temperatures]
-
A.
supportedRegime
Indicates that an entity provided assistance, endorsement, or backing to a particular political regime or government in power.
-
B.
regimeDefinedBy
Indicates that a particular regime is characterized, specified, or determined by another entity or set of rules.
-
C.
createdRegimeOf
Indicates that one entity brought about, established, or was responsible for the formation of a particular regime or system of rule for another entity.
-
D.
recognizesRegime
Indicates that one entity formally acknowledges the legitimacy or authority of another entity’s governing regime.
-
E.
validIn
chosen
Indicates that a given entity, statement, or condition is applicable, correct, or legally/semantically acceptable within a specified context, scope, or domain.
- 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.