Triple
T12135952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kristian Høgsberg |
E289056
|
entity |
| Predicate | softwareDevelopmentStyle |
P53448
|
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: [Kristian Høgsberg, softwareDevelopmentStyle, open-source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareDevelopmentStyle Context triple: [Kristian Høgsberg, softwareDevelopmentStyle, open-source]
-
A.
programmingStyle
Indicates the particular approach, methodology, or paradigm an entity uses when writing or organizing code.
-
B.
developmentStyle
chosen
Indicates the manner or approach in which something is developed, such as the methodology, process, or style guiding its creation or evolution.
-
C.
developmentMethod
Indicates the process, technique, or approach used to create, build, or evolve something.
-
D.
programmingCharacteristic
Indicates a relationship where an entity possesses or exhibits a particular property, trait, or quality specifically related to programming.
-
E.
softwareDomain
Indicates that something belongs to, operates within, or is associated with a particular area or field of software.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91841615c819097f20a7447a1b8f4 |
completed | April 10, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69d91508f8008190b3a90ec0bf0953ca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.