Triple
T2373634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ising model |
E46143
|
entity |
| Predicate | localFieldParameter |
P38772
|
FINISHED |
| Object | h_i |
—
|
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: h_i | Statement: [Ising model, localFieldParameter, h_i]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localFieldParameter Context triple: [Ising model, localFieldParameter, h_i]
-
A.
fieldPattern
Indicates a recurring or structured arrangement or configuration present within a field or area.
-
B.
locationScope
Indicates the specific geographic or spatial area within which a given relationship, condition, or action is considered valid or applicable.
-
C.
fieldName
Indicates the specific name or label assigned to a field within a data structure, form, or record.
-
D.
localityCondition
Indicates a spatial or contextual constraint specifying where or under what local conditions a relationship, event, or property holds.
-
E.
namedAfterField
Indicates that one entity has been given a name derived from or in honor of another entity, typically a person, place, or thing.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abca4c937c8190b4dfca716b868d4f |
completed | March 7, 2026, 6:48 a.m. |
Created at: March 4, 2026, 7:56 p.m.