Triple
T29107265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OneDep |
E736792
|
entity |
| Predicate | maintainsRelationshipWith |
P26922
|
FINISHED |
| Object | Protein Data Bank archive |
—
|
NE NERFINISHED |
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: Protein Data Bank archive | Statement: [OneDep, maintainsRelationshipWith, Protein Data Bank archive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainsRelationshipWith Context triple: [OneDep, maintainsRelationshipWith, Protein Data Bank archive]
-
A.
haveRelationshipWith
Indicates that one entity is in some form of defined relationship or association with another entity.
-
B.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
C.
maintainsTieWith
chosen
Indicates that one entity keeps an ongoing connection or relationship with another entity over time.
-
D.
laterRelationshipWith
Indicates that one entity has a relationship with another that occurs at a later time relative to some reference point or prior relationship.
-
E.
coversRelationship
Indicates that one entity extends over, includes, or provides encompassing coverage for another entity or set of entities.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 11:16 a.m.