Triple
T27840312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kay Sievers |
E703659
|
entity |
| Predicate | softwareDevelopmentModel |
P89307
|
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: [Kay Sievers, softwareDevelopmentModel, open source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareDevelopmentModel Context triple: [Kay Sievers, softwareDevelopmentModel, open source]
-
A.
developmentModelFor
chosen
Indicates that one entity serves as the development model, framework, or paradigm used to guide or structure the creation or evolution of another entity.
-
B.
softwareModel
Indicates that one entity serves as a software-based representation or abstraction (a model) of another entity or system.
-
C.
developmentMethod
Indicates the process, technique, or approach used to create, build, or evolve something.
-
D.
softwareParadigm
Indicates that a piece of software or a programming language follows or is based on a particular programming paradigm or style of development.
-
E.
developmentProcessIncludes
Indicates that a particular activity, phase, or component is part of, or contained within, a broader development process.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 6:02 p.m.