Triple
T18791150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heapsort |
E459516
|
entity |
| Predicate | sortingOrderSupport |
P133021
|
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, sortingOrderSupport, ascending]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sortingOrderSupport Context triple: [Heapsort, sortingOrderSupport, ascending]
-
A.
selectionOrderAdjustment
Indicates a modification to the original order in which items or options were selected, such as reordering or adjusting their selection sequence.
-
B.
hasOrderingMethod
Indicates that there is a specific method or procedure used to place or arrange an order for something.
-
C.
selectionOrderInfluencedBy
Indicates that the order in which items are selected is affected or determined by another factor, condition, or entity.
-
D.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
-
E.
confersOrder
Indicates that one entity formally bestows or grants an order, rank, or honorific distinction upon another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:53 a.m.