Triple

T4537417
Position Surface form Disambiguated ID Type / Status
Subject Heisenberg model E107439 entity
Predicate solvableInSpecialCase P7025 FINISHED
Object one-dimensional spin-1/2 chain 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: one-dimensional spin-1/2 chain | Statement: [Heisenberg model, solvableInSpecialCase, one-dimensional spin-1/2 chain]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: solvableInSpecialCase
Context triple: [Heisenberg model, solvableInSpecialCase, one-dimensional spin-1/2 chain]
  • A. specialCaseOf chosen
    Indicates that one entity represents a more specific, exceptional, or restricted instance of the general situation, rule, or relationship expressed by another entity.
  • B. admitsSolution
    Indicates that a problem, system, or situation allows for or possesses at least one valid solution.
  • C. commonlySolvedBy
    Indicates that a problem, task, or issue is typically addressed or resolved through a particular method, tool, or agent.
  • D. isSolutionOf
    Indicates that one entity is a correct answer or satisfies the conditions of a given problem, equation, or task.
  • E. solved
    Indicates that one entity has successfully found a solution or answer to a problem, task, or challenge involving another entity.
  • 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_69bd43f922788190b7edfa294e39b178 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd57b78b8481909d79131723d4be22 completed March 20, 2026, 2:20 p.m.
PD Predicate disambiguation batch_69bd521edd00819099dfccaa65dddd61 completed March 20, 2026, 1:56 p.m.
Created at: March 20, 2026, 1:04 p.m.