Triple
T23466588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Entrez |
E569116
|
entity |
| Predicate | locatedInInfrastructure |
P19374
|
FINISHED |
| Object | NCBI servers |
—
|
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: NCBI servers | Statement: [Entrez, locatedInInfrastructure, NCBI servers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInInfrastructure Context triple: [Entrez, locatedInInfrastructure, NCBI servers]
-
A.
containedInfrastructure
Indicates that one infrastructure element is physically or logically contained within another infrastructure element.
-
B.
isPartOfInfrastructure
chosen
Indicates that something belongs to, is included within, or functions as a component of a larger infrastructure system.
-
C.
usesInfrastructure
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
-
D.
ownedInfrastructureClass
Indicates that an entity possesses or controls infrastructure belonging to a specified class or category.
-
E.
isPartOfInfrastructureType
Indicates that something belongs to, or is categorized under, a specific type of infrastructure.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6fc35c48190a67614fb4170f15b |
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:54 p.m.