Triple
T18791159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heapsort |
E459516
|
entity |
| Predicate | supportsRandomAccessArray |
P34878
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Heapsort, supportsRandomAccessArray, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRandomAccessArray Context triple: [Heapsort, supportsRandomAccessArray, true]
-
A.
isRandomAccess
chosen
Indicates that the target can be accessed directly at arbitrary positions without needing to traverse preceding elements sequentially.
-
B.
canBeRandomized
Indicates that the entity is capable of having its state, order, or selection determined by a random process.
-
C.
supportsSeekableStreams
Indicates that an entity is capable of handling streams that allow seeking to arbitrary positions within the data.
-
D.
isRandomized
Indicates that the selection, ordering, or assignment associated with something is determined by a random process rather than a fixed or predetermined rule.
-
E.
supportsExtentBasedAllocation
Indicates that one entity provides or enables allocation of resources based on contiguous extents rather than fixed-size blocks.
- 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.