Triple
T6098422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCBI E-utilities API |
E135932
|
entity |
| Predicate | rateLimitedBy |
P20676
|
FINISHED |
| Object | NCBI usage policies |
—
|
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 usage policies | Statement: [NCBI E-utilities API, rateLimitedBy, NCBI usage policies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rateLimitedBy Context triple: [NCBI E-utilities API, rateLimitedBy, NCBI usage policies]
-
A.
supportsRateLimiting
Indicates that one entity provides or is compatible with mechanisms to restrict the rate at which another entity can perform actions or process requests.
-
B.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
C.
attemptLimit
Indicates a restriction on how many times an action or operation may be attempted before it is stopped or blocked.
-
D.
reasonForPerformanceLimitation
chosen
Indicates that one factor serves as the cause or explanation for why a performance limitation occurs.
-
E.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05a9a02888190ac201acd14c3fc31 |
completed | March 22, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.