Triple
T2373633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ising model |
E46143
|
entity |
| Predicate | interactionParameter |
P12016
|
FINISHED |
| Object | J_{ij} |
—
|
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: J_{ij} | Statement: [Ising model, interactionParameter, J_{ij}]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactionParameter
Context triple: [Ising model, interactionParameter, J_{ij}]
-
A.
parameter
chosen
Indicates that one entity serves as a parameter or argument that configures, constrains, or influences the behavior or outcome of another entity or process.
-
B.
interactionPoint
Indicates a specific location or moment where two or more entities come into contact or engage with each other.
-
C.
usageVariesBy
Indicates that the way something is used differs depending on a specified factor, such as context, user, location, or conditions.
-
D.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
E.
usesIntervention
Indicates that one entity applies, employs, or relies on a specific intervention (such as a treatment, method, or strategy) in relation to another entity or context.
- 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_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. |
Created at: March 4, 2026, 7:56 p.m.