Triple
T4537427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heisenberg model |
E107439
|
entity |
| Predicate | coreConceptIn |
P49381
|
FINISHED |
| Object | theory of magnetism |
—
|
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: theory of magnetism | Statement: [Heisenberg model, coreConceptIn, theory of magnetism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreConceptIn Context triple: [Heisenberg model, coreConceptIn, theory of magnetism]
-
A.
primaryConcept
chosen
Indicates that one concept is the main or central idea in relation to another concept or context.
-
B.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
C.
featuredConcept
Indicates that one concept is highlighted or given special prominence relative to others in a particular context.
-
D.
coreIdea
Indicates the central concept or primary message that underlies or unifies something, such as a text, argument, or work.
-
E.
operationalConcept
Indicates that one entity defines, specifies, or embodies the operational concept or way of functioning for 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.