Triple
T3691490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Double Helix |
E78353
|
entity |
| Predicate | involvesBasePair |
P46528
|
FINISHED |
| Object | adenine–thymine base pair |
—
|
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: adenine–thymine base pair | Statement: [The Double Helix, involvesBasePair, adenine–thymine base pair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesBasePair Context triple: [The Double Helix, involvesBasePair, adenine–thymine base pair]
-
A.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
B.
isPairOf
chosen
Indicates that two entities are associated as a matched or corresponding pair within a defined context.
-
C.
hasNumberOfHairpinTurns
Indicates the quantity of hairpin turns associated with an entity, such as a road or path.
-
D.
hasStrand
Indicates that one entity possesses or is associated with a particular strand or orientation relative to another entity.
-
E.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
- 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_69ad85e285a081908f8cbfa9e2ed9b75 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4e783a88190b2837a68b8723a25 |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.