Triple
T9838772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Bruijn graph |
E239167
|
entity |
| Predicate | typicalEdgeDefinition |
P57083
|
FINISHED |
| Object | k-mer whose prefix and suffix are vertices |
—
|
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: k-mer whose prefix and suffix are vertices | Statement: [de Bruijn graph, typicalEdgeDefinition, k-mer whose prefix and suffix are vertices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEdgeDefinition Context triple: [de Bruijn graph, typicalEdgeDefinition, k-mer whose prefix and suffix are vertices]
-
A.
typicalEdge
chosen
Indicates a standard or representative connection between two entities, as opposed to a special or exceptional type of edge.
-
B.
standardEdge
Indicates a basic or default connection or link between two entities, without any special properties or conditions.
-
C.
edgeType
Indicates the specific kind or category of connection that exists between two related entities.
-
D.
formsEdgeOf
Indicates that one entity constitutes a boundary or outer limit of another entity.
-
E.
typicalBoundary
Indicates that one entity serves as the usual or characteristic boundary or limit for 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb34921b881909836ba0f5b42a27b |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.