Triple
T23313204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The NetBSD Foundation |
E590635
|
entity |
| Predicate | softwareTypeSupported |
P48616
|
FINISHED |
| Object | Unix-like operating systems |
—
|
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: Unix-like operating systems | Statement: [The NetBSD Foundation, softwareTypeSupported, Unix-like operating systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareTypeSupported Context triple: [The NetBSD Foundation, softwareTypeSupported, Unix-like operating systems]
-
A.
softwareIncluded
Indicates that certain software is bundled with, provided alongside, or contained within another item or offering.
-
B.
supportedIn
chosen
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
C.
hasSoftwareType
Indicates that an entity is associated with or classified under a particular type or category of software.
-
D.
hasSoftwareCompatibilityWith
Indicates that one software system can operate correctly and effectively with another software system, without conflicts or required modifications.
-
E.
softwareFormat
Indicates that one entity specifies or uses the file or data format in which a software-related item is encoded, stored, or delivered.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972ca70481909e2415c65964210a |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:06 p.m.