Triple
T19467218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | t-J model |
E487030
|
entity |
| Predicate | describesPhase |
P136030
|
FINISHED |
| Object | antiferromagnetic order |
—
|
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: antiferromagnetic order | Statement: [t-J model, describesPhase, antiferromagnetic order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesPhase Context triple: [t-J model, describesPhase, antiferromagnetic order]
-
A.
PhaseIDescribes
Indicates that one entity provides a description or characterization of a specific phase (Phase I) of another entity or process.
-
B.
isPartOfPhase
Indicates that something belongs to, occurs within, or constitutes a component of a specific phase in a larger process or lifecycle.
-
C.
codeNameOfPhase
Indicates that an entity is assigned a specific code name corresponding to a particular phase in a process or lifecycle.
-
D.
targetsPhase
Indicates that an action, process, or entity is specifically directed toward or intended to affect a particular phase or stage within a larger sequence or lifecycle.
-
E.
phasesOut
Indicates the process by which one entity or condition is gradually discontinued or removed in favor of another over time.
- 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.