Triple
T23472977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GenBank |
E570176
|
entity |
| Predicate | isPrimaryResourceFor |
P70057
|
FINISHED |
| Object | genetic research |
—
|
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: genetic research | Statement: [GenBank, isPrimaryResourceFor, genetic research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryResourceFor Context triple: [GenBank, isPrimaryResourceFor, genetic research]
-
A.
isResourceFor
chosen
Indicates that one entity serves as a resource, support, or means of use for another entity.
-
B.
primaryResourceType
Indicates the main or predominant type/category of resource associated with an entity or activity.
-
C.
basedOnResource
Indicates that one entity is derived from, created using, or conceptually dependent on another entity as its underlying resource.
-
D.
isPrimaryReservationOf
Indicates that a given reservation is the main or designated primary booking associated with a particular entity (such as a person, account, or resource).
-
E.
isServedFor
Indicates that something is provided or presented as suitable or intended for a particular purpose, use, or recipient.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a70244208190bbd8f58ac16d4399 |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:57 p.m.