Triple
T29689897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BLAG (historical) |
E751184
|
entity |
| Predicate | softwareFreedomFocus |
P162628
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [BLAG (historical), softwareFreedomFocus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareFreedomFocus Context triple: [BLAG (historical), softwareFreedomFocus, yes]
-
A.
softwareFreedomStatus
Indicates the degree to which a piece of software respects users’ freedoms to use, study, modify, and share it.
-
B.
FSFApproved
Indicates that something has been reviewed and approved by the Free Software Foundation as meeting its free software licensing criteria.
-
C.
openSource
Indicates that the subject makes its source code publicly available under a license that allows others to use, modify, and redistribute it.
-
D.
softwareCategoryFocus
chosen
Indicates that something is primarily concerned with, or directed toward, a particular category or type of software.
-
E.
softwareFor
Indicates that one entity is designed, intended, or used to operate on, support, or be compatible with another entity as 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672938e18819082394196f97e6340 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 7:16 p.m.