Triple
T18051232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | heapq |
E431929
|
entity |
| Predicate | supportsCustomPriority |
P55285
|
FINISHED |
| Object | via tuple keys |
—
|
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: via tuple keys | Statement: [heapq, supportsCustomPriority, via tuple keys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCustomPriority Context triple: [heapq, supportsCustomPriority, via tuple keys]
-
A.
supportsPriority
chosen
Indicates that one entity provides functionality or capability for handling or honoring priority levels associated with another entity or operation.
-
B.
upgradePriority
Indicates the relative importance or urgency assigned to performing an upgrade compared to other potential upgrades or tasks.
-
C.
identifiesAsPriorityUses
Indicates that one entity designates or treats another entity as a priority for use or utilization.
-
D.
hasPriorityAt
Indicates that one entity holds a specified level of priority or precedence at a particular time, place, or context relative to others.
-
E.
upgradePriorityBasedOn
Indicates that the priority level of something is increased or adjusted according to the status, attributes, or importance of another specified factor or entity.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c0fe4f1881908fa8485cb3ccfa44 |
completed | April 19, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.