Triple
T33056629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DD-WRT |
E845862
|
entity |
| Predicate | hasSourceModel |
P43872
|
FINISHED |
| Object | open source |
—
|
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: open source | Statement: [DD-WRT, hasSourceModel, open source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceModel Context triple: [DD-WRT, hasSourceModel, open source]
-
A.
hasMainSource
Indicates that one entity serves as the primary or principal source or origin for another entity.
-
B.
hasComponentModel
chosen
Indicates that an entity includes or is associated with a specific component model as part of its structure or configuration.
-
C.
hasSourceOfData
Indicates that one entity serves as the origin or provider of the data used or referenced by another entity.
-
D.
hasParentAccordingToSource
Indicates that an entity is recorded as the parent of another entity according to a specified source or authority.
-
E.
hasDefinitionSource
Indicates that the definition of an entity originates from or is documented in a specified source.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 1, 2026, 1:25 a.m.