Triple
T380018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cooper pair |
E8656
|
entity |
| Predicate | isDescribedIn |
P519
|
FINISHED |
| Object | many-body quantum theory |
—
|
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: many-body quantum theory | Statement: [Cooper pair, isDescribedIn, many-body quantum theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDescribedIn Context triple: [Cooper pair, isDescribedIn, many-body quantum theory]
-
A.
describedIn
chosen
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
B.
describes
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
C.
describedByAuthorAs
Indicates that one entity is characterized, labeled, or portrayed in a particular way by an author.
-
D.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
E.
presentedInLanguage
Indicates that something (such as content, information, or a work) is expressed or made available using a particular language.
- 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.