Triple
T11074210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNA ligase |
E261823
|
entity |
| Predicate | localizesTo |
P93283
|
FINISHED |
| Object | nucleus |
—
|
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: nucleus | Statement: [DNA ligase, localizesTo, nucleus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localizesTo Context triple: [DNA ligase, localizesTo, nucleus]
-
A.
localizationBy
Indicates a relationship where one entity determines, specifies, or constrains the spatial or contextual location of another entity.
-
B.
localization
chosen
Indicates the spatial or contextual placement of one entity relative to another or within a specific environment.
-
C.
isLocalizable
Indicates that something can be adapted or translated to different languages or locales without losing its intended function or meaning.
-
D.
localizationSignal
Indicates that one entity provides or serves as a signal that directs the localization or spatial positioning of another entity.
-
E.
locale
Indicates that one entity is the place, setting, or geographic area in which another entity exists, occurs, or is situated.
- 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.