Triple
T32196266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | programmed cell death protein 1 |
E822411
|
entity |
| Predicate | pdbStructureAvailable |
P173313
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [programmed cell death protein 1, pdbStructureAvailable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pdbStructureAvailable Context triple: [programmed cell death protein 1, pdbStructureAvailable, true]
-
A.
solutionStructure
Indicates the structural or compositional arrangement that characterizes how a solution is organized or configured.
-
B.
hasQuaternaryStructure
Indicates that a protein is composed of multiple polypeptide chains (subunits) arranged in a specific spatial relationship to form a functional complex.
-
C.
bestKnownStructure
Indicates that the related entity is the most prominent or widely recognized structure associated with the subject.
-
D.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
E.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
- F. None of above. chosen
Provenance (4 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb3795fc8190bfcb00d45aa887a1 |
completed | May 3, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b42902a081909126c7322858a2b3 |
completed | May 3, 2026, 2:34 a.m. |
Created at: May 1, 2026, 12:36 a.m.