Triple
T33056691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DD-WRT |
E845862
|
entity |
| Predicate | hasDistributionVariant |
P198086
|
FINISHED |
| Object | micro build |
—
|
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: micro build | Statement: [DD-WRT, hasDistributionVariant, micro build]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistributionVariant Context triple: [DD-WRT, hasDistributionVariant, micro build]
-
A.
hasDistributionType
Indicates the type or pattern of distribution associated with an entity, specifying how something is spread, allocated, or made available.
-
B.
hasDistributions
Indicates that an entity is associated with one or more distributions through which it is delivered, provided, or made available.
-
C.
hasDistributionForm
Indicates that an entity is associated with a particular physical or pharmaceutical form in which it is distributed or made available.
-
D.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
-
E.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69fec8adaa308190a9a276f8c36f15f0 |
completed | May 9, 2026, 5:39 a.m. |
Created at: May 1, 2026, 1:25 a.m.