Triple
T11074183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNA ligase |
E261823
|
entity |
| Predicate | biochemicalReactionType |
P69657
|
FINISHED |
| Object | ligation of DNA strand breaks |
—
|
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: ligation of DNA strand breaks | Statement: [DNA ligase, biochemicalReactionType, ligation of DNA strand breaks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biochemicalReactionType Context triple: [DNA ligase, biochemicalReactionType, ligation of DNA strand breaks]
-
A.
reactionType
chosen
Indicates the specific kind or category of reaction that occurs between entities or in response to an event or stimulus.
-
B.
enzymeType
Indicates the specific class or category of enzyme associated with an entity or reaction.
-
C.
firstSynthesisReactionType
Indicates the type or category of the initial synthesis reaction that occurs or is applied in a given process or pathway.
-
D.
fusionReactionType
Indicates the specific kind or category of nuclear fusion process that relates two or more participating entities.
-
E.
ringReaction
Indicates that one entity performs or undergoes a reaction involving a chemical ring structure in relation to another entity.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7994e32fc8190a6591d9e82b68f75 |
completed | April 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.