Triple
T380097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meissner effect |
E8658
|
entity |
| Predicate | behaviorInTypeII |
P662
|
FINISHED |
| Object | partial flux penetration via vortices between Hc1 and Hc2 |
—
|
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: partial flux penetration via vortices between Hc1 and Hc2 | Statement: [Meissner effect, behaviorInTypeII, partial flux penetration via vortices between Hc1 and Hc2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: behaviorInTypeII Context triple: [Meissner effect, behaviorInTypeII, partial flux penetration via vortices between Hc1 and Hc2]
-
A.
behaviorNear
Indicates that one entity exhibits a behavior or action in close spatial proximity to another entity.
-
B.
limitBehavior
Indicates how an entity behaves or changes as it approaches a specified limit or boundary condition.
-
C.
decayMode
Indicates the specific process or pathway by which an unstable entity transforms or decays into other products.
-
D.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
E.
secondPhase
Indicates that an entity is in, or has progressed to, the second phase or stage of a multi-phase process or sequence.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2b07248190979229bad3a741c9 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e964d4b481909290e474b0341e3c |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.