Triple
T2792708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNU Awk |
E61964
|
entity |
| Predicate | licenseVersion |
P2182
|
FINISHED |
| Object | GPLv3 or later |
—
|
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: GPLv3 or later | Statement: [GNU Awk, licenseVersion, GPLv3 or later]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenseVersion Context triple: [GNU Awk, licenseVersion, GPLv3 or later]
-
A.
licenseBuiltAs
Indicates that one entity is constructed, configured, or deployed under the terms or identity of another entity’s license.
-
B.
licenseModel
Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
-
C.
licenseFamily
chosen
Indicates that one license belongs to, is derived from, or is categorized under a broader family or class of related licenses.
-
D.
licenseBuiltIn
Indicates that a license is inherently included within or comes standard as part of another product, service, or system rather than being added separately.
-
E.
licenseBuiltFrom
Indicates that a license is derived from, or constructed based on, another underlying license or licensing template.
- 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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdeea881481908d759c72798a50fb |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd025c948190a97dd961a9592bac |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.