Triple
T26296999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OverDrive |
E661443
|
entity |
| Predicate | supportsHoldQueues |
P79890
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [OverDrive, supportsHoldQueues, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHoldQueues Context triple: [OverDrive, supportsHoldQueues, yes]
-
A.
hasQueue
Indicates that an entity maintains or is associated with a queue, typically representing an ordered list of items or tasks awaiting processing.
-
B.
hasQueueRequirement
Indicates that an entity must satisfy or adhere to a specified queue-related condition or rule.
-
C.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
D.
usesQueue
chosen
Indicates that one entity employs or relies on a queue mechanism to manage or process items, tasks, or messages.
-
E.
hasQueueType
Indicates that an entity is associated with a specific type or category of queue.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: April 26, 2026, 10:13 p.m.