Triple
T36199057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prim's minimum spanning tree algorithm |
E1047207
|
entity |
| Predicate | dataStructureOption |
P32204
|
FINISHED |
| Object | priority queue |
—
|
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: priority queue | Statement: [Prim's minimum spanning tree algorithm, dataStructureOption, priority queue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataStructureOption Context triple: [Prim's minimum spanning tree algorithm, dataStructureOption, priority queue]
-
A.
storageStructure
Indicates a relationship where one entity serves as a physical or logical structure used to store or contain another entity.
-
B.
usesDataStructure
chosen
Indicates that one entity employs or relies on a particular data structure in its operation or implementation.
-
C.
collectionStructure
Indicates how elements within a collection are organized, arranged, or related to one another.
-
D.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
E.
displayStructure
Indicates that one entity presents or reveals the internal organization, layout, or arrangement of another entity.
- 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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.