Triple
T6790279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghostscript |
E155913
|
entity |
| Predicate | dualLicensed |
P73009
|
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: [Ghostscript, dualLicensed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dualLicensed Context triple: [Ghostscript, dualLicensed, true]
-
A.
hasLicensing
Indicates that one entity holds or is granted licensing rights, permissions, or authorization in relation to another entity or resource.
-
B.
previouslyLicensedAs
Indicates that an entity held a license under a different name or status at some earlier time.
-
C.
canBeLicensedUnder
Indicates that something is eligible or suitable to be granted a particular legal license or licensing terms.
-
D.
licenseBuiltAs
Indicates that one entity is constructed, configured, or deployed under the terms or identity of another entity’s license.
-
E.
requiresLicenseOf
Indicates that one entity must obtain or hold the license associated with another entity in order to use, access, or perform something.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2ab4ce88190b6311e4d5aac758c |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1b0d2a48190b249dcc671b9b5e4 |
completed | March 27, 2026, 6:51 p.m. |
Created at: March 27, 2026, 2:15 p.m.