Triple
T25111719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bacteriophage lambda |
E629012
|
entity |
| Predicate | hasCohesiveEnds |
P175941
|
FINISHED |
| Object | cos sites |
—
|
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: cos sites | Statement: [bacteriophage lambda, hasCohesiveEnds, cos sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCohesiveEnds Context triple: [bacteriophage lambda, hasCohesiveEnds, cos sites]
-
A.
hasCabAtEachEnd
Indicates that something (typically a vehicle or train) has a cab located at both of its ends.
-
B.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
-
C.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
D.
hasEndCones
Indicates that an object possesses cone-shaped elements at one or both of its ends.
-
E.
hasNoBeginningOrEnd
Indicates that the related entity exists without a starting point or ending point in time or extent.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 18, 2026, 6:27 a.m.