Triple
T380087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meissner effect |
E8658
|
entity |
| Predicate | explainedBy |
P3638
|
FINISHED |
| Object | London theory of superconductivity |
—
|
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: London theory of superconductivity | Statement: [Meissner effect, explainedBy, London theory of superconductivity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explainedBy Context triple: [Meissner effect, explainedBy, London theory of superconductivity]
-
A.
usedToExplain
chosen
Indicates that one entity serves as an explanation or clarification for another entity.
-
B.
aimsToExplain
Indicates that one entity intends to clarify, make understandable, or provide an explanation about another entity, concept, or situation.
-
C.
doesNotFullyExplain
Indicates that one entity’s explanation of another entity, event, or situation is incomplete or insufficient to account for it fully.
-
D.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
-
E.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
- 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.