Triple
T14930921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apache License 1.0 |
E372260
|
entity |
| Predicate | containsPatentGrant |
P116714
|
FINISHED |
| Object | no (explicit) |
—
|
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: no (explicit) | Statement: [Apache License 1.0, containsPatentGrant, no (explicit)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPatentGrant Context triple: [Apache License 1.0, containsPatentGrant, no (explicit)]
-
A.
hasPatentGrant
Indicates that a patent grant exists conferring legal protection or rights to an entity for a specific invention or intellectual property.
-
B.
grantedPatentAs
Indicates that a patent has been officially granted to an entity in a specified role or capacity.
-
C.
typeOfPatentsGranted
Indicates the specific categories or kinds of patents that have been officially granted to an entity.
-
D.
isPatentEncumbered
Indicates that the subject is restricted or burdened by existing patent rights that limit its free use, distribution, or implementation.
-
E.
hasPatentPortfolioIn
Indicates that an entity holds or manages one or more patents within a specified jurisdiction, region, or technical 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64550dc8190ba44120df00ba498 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:36 a.m.