Triple
T18791214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Insertion sort |
E459517
|
entity |
| Predicate | processesElements |
P133028
|
FINISHED |
| Object | left to right |
—
|
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: left to right | Statement: [Insertion sort, processesElements, left to right]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processesElements Context triple: [Insertion sort, processesElements, left to right]
-
A.
usesProcessDocument
Indicates that an entity employs or relies on a specific process document as part of performing an action or carrying out a procedure.
-
B.
incorporatesElementsFrom
Indicates that one entity includes or integrates components, features, or aspects derived from another entity.
-
C.
usesElementsOf
Indicates that one entity incorporates, applies, or draws upon components, principles, or features derived from another entity.
-
D.
processNode
Indicates performing an operation or series of operations on a node within a data structure or system.
-
E.
featuresElementSystem
Indicates that a system includes or incorporates a particular element as one of its constituent parts or components.
- 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.