Triple
T6042380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FreeRTOS |
E134577
|
entity |
| Predicate | previousLicense |
P48641
|
FINISHED |
| Object | Modified GPL license |
—
|
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: Modified GPL license | Statement: [FreeRTOS, previousLicense, Modified GPL license]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousLicense Context triple: [FreeRTOS, previousLicense, Modified GPL license]
-
A.
previousLicenseModel
chosen
Indicates that an entity was governed by a different license model before the current one.
-
B.
previouslyLicensedAs
Indicates that an entity held a license under a different name or status at some earlier time.
-
C.
formerCityOfLicense
Indicates that an entity previously held, but no longer holds, the official city of license designation for another entity (typically a broadcast station).
-
D.
hasLicense
Indicates that an entity possesses a valid authorization or permit, typically granted by an authority, to perform a specific activity or use something.
-
E.
previousLegalForm
Indicates the legal form or organizational status an entity had before its current legal form.
- 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_69c00876a69881908088a2626d3b2666 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056e108fc81908775d176ff960fad |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049eb52a08190ac10fd703735f5aa |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.