Triple
T19467226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | t-J model |
E487030
|
entity |
| Predicate | HamiltonianContains |
P136031
|
FINISHED |
| Object | projected hopping term |
—
|
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: projected hopping term | Statement: [t-J model, HamiltonianContains, projected hopping term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HamiltonianContains Context triple: [t-J model, HamiltonianContains, projected hopping term]
-
A.
LagrangianContains
Indicates that a given term, field, or interaction is included as part of the Lagrangian in a physical or mathematical model.
-
B.
hasBasisIn
Indicates that one entity is founded, derived, or justified on the grounds of another entity.
-
C.
hasLagrangian
Indicates that a physical system or theory is associated with a specific Lagrangian function that characterizes its dynamics.
-
D.
holdsIn
Indicates that a relationship, condition, or event is valid or occurs within a specified time interval or temporal context.
-
E.
spectrumContains
Indicates that a given spectrum includes or exhibits a specified component, feature, or range within it.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e2aee081908330a5665fa60482 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:39 p.m.