Triple
T4555122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PHP License |
E120461
|
entity |
| Predicate | isFSFApproved |
P16203
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [PHP License, isFSFApproved, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFSFApproved Context triple: [PHP License, isFSFApproved, true]
-
A.
FSFApproved
chosen
Indicates that something has been reviewed and approved by the Free Software Foundation as meeting its free software licensing criteria.
-
B.
softwareFreedomStatus
Indicates the degree to which a piece of software respects users’ freedoms to use, study, modify, and share it.
-
C.
isGPLCompatible
Indicates that a software license is legally compatible with the GNU General Public License (GPL), allowing code to be combined and distributed under GPL terms.
-
D.
isCopyleft
Indicates that the subject is governed by a copyleft license, requiring derivative works to be distributed under the same or compatible licensing terms.
-
E.
OSIApproved
Indicates that a software license has been reviewed and approved by the Open Source Initiative (OSI) as complying with its Open Source Definition.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd5813af948190b10b02dadf6496bf |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd5223423c81908317351b58cff5f5 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.