Triple
T29689706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PureOS |
E751180
|
entity |
| Predicate | repositoryPolicy |
P167597
|
FINISHED |
| Object | only free software |
—
|
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: only free software | Statement: [PureOS, repositoryPolicy, only free software]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repositoryPolicy Context triple: [PureOS, repositoryPolicy, only free software]
-
A.
revisionPolicy
Indicates the rules or procedures governing how and when something (such as a document, plan, or item) may be updated, changed, or versioned over time.
-
B.
collectionPolicy
Indicates the rules or guidelines that govern how items are gathered, selected, and managed within a collection.
-
C.
referencePolicy
Indicates that one entity defines rules or guidelines governing how another entity may be referred to, cited, or mentioned.
-
D.
publicPolicy
Indicates that an entity is a government or institutional rule, principle, or course of action intended to address public issues or guide societal outcomes.
-
E.
issuesPolicyOn
Indicates that an authority or organization formally creates, approves, or enacts a policy concerning a particular subject or domain.
- F. None of above. chosen
Provenance (4 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_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 7:15 p.m.