Triple
T18051231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | heapq |
E431929
|
entity |
| Predicate | orderingBasis |
P37518
|
FINISHED |
| Object | Python object comparison |
—
|
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: Python object comparison | Statement: [heapq, orderingBasis, Python object comparison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderingBasis Context triple: [heapq, orderingBasis, Python object comparison]
-
A.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
-
B.
orderOf
chosen
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
C.
orderDefinitionBasedOn
Indicates that one item’s definition or specification is arranged, derived, or structured based on the definition or specification of another item.
-
D.
orderType
Indicates the specific category or classification of an order, such as its purpose, channel, or processing method.
-
E.
orden
Indicates that one entity issues, gives, or establishes an order, command, or directive concerning another entity or situation.
- 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.