Triple
T22932272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EInfo |
E569471
|
entity |
| Predicate | endpointURLPattern |
P49348
|
FINISHED |
| Object | https://eutils.ncbi.nlm.nih.gov/entrez/eutils/einfo.fcgi |
—
|
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: https://eutils.ncbi.nlm.nih.gov/entrez/eutils/einfo.fcgi | Statement: [EInfo, endpointURLPattern, https://eutils.ncbi.nlm.nih.gov/entrez/eutils/einfo.fcgi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endpointURLPattern Context triple: [EInfo, endpointURLPattern, https://eutils.ncbi.nlm.nih.gov/entrez/eutils/einfo.fcgi]
-
A.
typicalEndpoint
Indicates that something represents the standard or commonly used endpoint associated with another entity or process.
-
B.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
C.
endpointFeature
Indicates that a particular feature, capability, or characteristic is associated with, provided by, or available at a specific endpoint.
-
D.
secondaryEndpoint
Indicates that something serves as an additional, non-primary endpoint or target associated with a main endpoint in a relationship or process.
-
E.
URLPattern
chosen
Indicates that a resource or endpoint is identified or matched by a specific structured web address pattern.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1813260608190bb9e1ca704c7e12f |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:44 p.m.