Triple
T181122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TeamViewer |
E3877
|
entity |
| Predicate | licensingModel |
P2182
|
FINISHED |
| Object | freemium |
—
|
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: freemium | Statement: [TeamViewer, licensingModel, freemium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licensingModel Context triple: [TeamViewer, licensingModel, freemium]
-
A.
licenseFamily
chosen
Indicates that one license belongs to, is derived from, or is categorized under a broader family or class of related licenses.
-
B.
license
Indicates that one entity has granted another entity formal permission or authorization to use, perform, or exploit something under specified terms.
-
C.
fundingModel
Indicates how an entity is financially supported or sustained, such as through specific revenue sources, payment structures, or funding mechanisms.
-
D.
publishingModel
Indicates the method or framework by which content is produced, distributed, and made publicly available.
-
E.
governanceModel
Indicates the type or structure of authority, decision-making, and control that defines how an entity is directed and overseen.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25923507c8190bd7f6eda404b0da0 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566ccc288190add5624ede96d82b |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.