Triple
T32062185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Licensing |
E818773
|
entity |
| Predicate | operatedInDomain |
P201408
|
FINISHED |
| Object | standard-essential patent licensing |
—
|
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: standard-essential patent licensing | Statement: [Via Licensing, operatedInDomain, standard-essential patent licensing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInDomain Context triple: [Via Licensing, operatedInDomain, standard-essential patent licensing]
-
A.
operatedInRegion
Indicates that an entity conducted operations or activities within a specified geographic region.
-
B.
isOperatedIn
Indicates that an entity carries out its operations or activities within a specified location, region, or jurisdiction.
-
C.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
D.
operatedInNetwork
Indicates that an entity carried out its activities or services within a specified network or system.
-
E.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fff328ddc0819080642334a41fcf95 |
completed | May 10, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69fff2e0971c819081aa66f4a6a34b28 |
completed | May 10, 2026, 2:52 a.m. |
| PDg | Predicate description generation | batch_69fff327d7788190a41ea5cbae060177 |
completed | May 10, 2026, 2:53 a.m. |
Created at: May 1, 2026, 12:22 a.m.