Triple
T18791186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heapsort |
E459516
|
entity |
| Predicate | outputOrderForMaxHeap |
P37518
|
FINISHED |
| Object | ascending |
—
|
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: ascending | Statement: [Heapsort, outputOrderForMaxHeap, ascending]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputOrderForMaxHeap Context triple: [Heapsort, outputOrderForMaxHeap, ascending]
-
A.
supportsMaxHeap
Indicates that one entity provides the necessary functionality or guarantees to correctly maintain and operate a max-heap data structure for another entity.
-
B.
orderOf
chosen
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
C.
displayOrder
Indicates the sequence or position in which items should be presented or shown relative to one another.
-
D.
hasLargestElementOrder
Indicates that, among a set of elements (typically group elements), one element has an order that is greater than or equal to the order of every other element in the set.
-
E.
joinedOrderOf
Indicates that an entity became a member of, or formally joined, a particular order or organization.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5978665388190aaefed0ec30a1ff3 |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.